Is it really always safe to combine packages that depend on one base
with packages that depend on another? My guess is "no, but ghc will
catch any compatibility issues", so the cabal warning perhaps shouldn't
be dropped?
As far as I can see the answer is yes but I'd be interested to see a
counter-example.
The reason it is supposed to be safe is that base-3 _only_ re-exports
base-4 and syb, right? So it is not just a question of base-3 directly
depending on base-4, but of base-3 being nothing but a different path
to the same code. Ok, makes sense.
I was not sure how that plays with the recent syb updates: base-3
depends on base-4+syb-0.1, and syb-0.1 depends on base-4, but
as long as that only makes for longer import chains (no duplicated
definitions) that should still be ok.
Claus
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
