GHC's module hierarchy

[Sylvain Henry]

Hi all,

We are back at considering an overhaul of the module structure of GHC. 
Ticket #13009 <https://gitlab.haskell.org/ghc/ghc/issues/13009> [1] is 
the place where the discussion takes place: this is a call for 
participation to this discussion!

Thanks,
Sylvain

PS: this work was supposed to be step 1 of a larger effort to make GHC 
more modular. See the wiki page 
<https://gitlab.haskell.org/ghc/ghc/wikis/Make-GHC-codebase-more-modular> 
[2] for more details and don't hesitate to give some feedback.

[1] https://gitlab.haskell.org/ghc/ghc/issues/13009
[2] https://gitlab.haskell.org/ghc/ghc/wikis/Make-GHC-codebase-more-modular


On 15/06/2017 09:41, Simon Peyton Jones via ghc-devs wrote:
>
> Dear ghc-devs
>
> hsyl20 proposes a radical overhaul of the module structure of GHC 
> itself.  He or she suggested it six months ago in
>
> https://ghc.haskell.org/trac/ghc/ticket/13009 
> <https://ghc.haskell.org/trac/ghc/ticket/13009>
>
> and has now offered a monster patch
>
> https://phabricator.haskell.org/D3647 
> <https://phabricator.haskell.org/D3647>
>
> It’s clearly the result of a lot of work, but I was the only one who 
> responded on the original ticket, and it’ll affect all of your lives 
> in a very immediate way.
>
> So, would you like to
>
> ·consider the idea
>
> ·look at the actual re-mapping of modules hsyl20 proposals
>
> ·express an opinion about whether to go ahead
>
> Probably the ticket, rather than Phab, is the best place to comment on 
> the general idea.
>
> I’d like to thank hsyl20.  GHC’s rather flat module structure has 
> grown incrementally over years.
>
> But still, there are pros and cons.
>
> Simon
>
>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20191002/aed00494/attachment.html>