search

jcristovao / newtype-generics

A typeclass and set of functions for working with newtypes.
10 stars 11 forks source link

Namespace collisions #1

Open crockeea opened 10 years ago

crockeea commented 10 years ago

While this package is great and supercedes the 'newtype' package, 'newtype' was first to the party and has already claimed the Control.Newtype module name. I have newtype installed as a dependency for syntactic-2.0, type-natural-0.2.3.1, and constraints-0.4, so when I import Control.Newtype, GHC complains that the module name is ambiguous.

The only solution I'm aware of would be using package qualified imports

I propose moving this package to Control.Newtype.Generic or something similar, like the approach taken here.

jcristovao commented 10 years ago

Hi, I certainly agree this is a problem. I've made one last attempt to contact the original newtype package to include my generics code, but previous attempts on my part were unsuccessful.

If no answer arrives, I'll go forward with your suggestion, thanks!

sjakobi commented 7 years ago

@crockeea Do you still run into these module name collisions these days? The packages that you listed seem to have removed their dependencies on newtype.

From a cursory look it also seems to me that only a few of newtype's reverse dependencies have recent uploads, giving me hope that fewer and fewer people will have newtype in their dependency graphs.

crockeea commented 7 years ago

No, I'm no longer using this package since the issue wasn't resolved.

sjakobi commented 6 years ago

I've finally changed my mind on this issue, moved the code to Control.Newtype.Generics, and deprecated Control.Newtype.

See the new release.