On Mon, Jul 15, 2013 at 12:22 PM, Henning Thielemann
<lemming@henning-thielemann.de> wrote:
On Mon, 15 Jul 2013, Joachim Breitner wrote:
The problem
===========
currently, base is a big beast that mixes a lot of different aspects,
from really basic stuff like Data.List to quite specific system
libraries like System.Console.GetOpt to gory GHC details such as
GHC.Conc.Signal. There are various issues with this:
* No implementation of a module included in base is able to use
stuff from other libraries, like containers. There are even
copies of container code in base.
* Changes to the API of obscure modules like GHC.Conc.Signal
require version bumps in base, which cause lots of depending
packages to upload new version just to change their dependency.
* The large expose surface of base makes refactoring like the
actual split of the base implementation harder.
* Compilers like haste or fay have a hard time providing a proper
base, as many of the modules do not make sense in that setting.
How is your proposal related to your SplitBase effort:
http://ghc.haskell.org/trac/ghc/wiki/SplitBase
?
_______________________________________________
Libraries mailing list
Libraries@haskell.org
http://www.haskell.org/mailman/listinfo/libraries