Yves Parès <limestr...@gmail.com> wrote: > > Fragmenting Hackage is bad. But on the other hand I don't see why I > > should stick with the inconvenient mtl. Open source software is all > > about choice, and as long as the mtl fails to provide the same > > flexibility and convenience, I won't use it. Combined with the fact > > that fixing it would break existing packages, it appears like I > > won't go back to the mtl ever. > > So tell me how you do when you have to use a package which relies on > mtl's transformers? > You re-develop the package?
So far this has never been a problem. These packages always came along with custom running and access functions. If that wasn't the case, well, I would choose the ugly way through qualified imports, but this has never happened to me: import qualified Control.Monad.Trans as MTL import MonadLib Greets, Ertugrul -- nightmare = unsafePerformIO (getWrongWife >>= sex) http://ertes.de/ _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe