If we're just talking about building one or two transformers then I'd say we should avoid incurring the dependency. The outcry would far far outweigh the code sharing advantage for one or two types. E.g. base duplicates State internally for mapAccumL for instance for this sort of reason.
Sent from my iPad > On Jun 22, 2016, at 12:58 PM, David Feuer <david.fe...@gmail.com> wrote: > > Currently, containers does not depend on transformers, so it has to duplicate > its functionality or just do without. Since transformers is also a GHC boot > package, I believe it should be feasible to make containers depend on it. To > what extent would that reduce > parallelizability of GHC builds or otherwise make people mad? > > David > _______________________________________________ > Libraries mailing list > librar...@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
