#1338: base package breakup
----------------------------+-----------------------------------------------
Reporter: simonmar | Owner: igloo
Type: task | Status: new
Priority: normal | Milestone: 6.10 branch
Component: libraries/base | Version: 6.6.1
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Architecture: Unknown
Os: Unknown |
----------------------------+-----------------------------------------------
Comment (by igloo):
One advantage of making base small is that if you are, for example,
debugging GHC.Handle then you don't have to recompile >100 other modules
every time you make a change in it.
Being able to separately upgrade the different parts is another advantage.
Also, it means that we can have a separate maintainer for, e.g., SYB
(well, this doesn't technically need it to be a separate package, but it's
conceptually simpler if it is).
Breaking base up into packages also makes it much easier to see what the
hierarchy is, and makes it easier to restructure the hierarchy. Plus it
means that people can't re-tangle the logically separate components, which
is all too easy to do when you just have one huge package.
It also means that packages are clearer about what they depend on. One
possibility, which I think would be really cool, is to separate all the IO
modules from the non-IO modules; between that and looking at the
extensions used (e.g. TH and FFI) it would then be clear whether or not a
library could do any IO. Of course, the Prelude is a hurdle for this goal.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1338#comment:18>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
