[GHC] #13009: Hierarchical Module Structure for GHC
GHC
ghc-devs at haskell.org
Thu Jun 15 14:15:02 UTC 2017
#13009: Hierarchical Module Structure for GHC
-------------------------------------+-------------------------------------
Reporter: hsyl20 | Owner: hsyl20
Type: task | Status: patch
Priority: low | Milestone:
Component: Compiler | Version: 8.0.1
Resolution: | Keywords:
Operating System: Unknown/Multiple | Architecture:
| Unknown/Multiple
Type of failure: None/Unknown | Test Case:
Blocked By: | Blocking:
Related Tickets: | Differential Rev(s): Phab:D3647
Wiki Page: |
ModuleDependencies/Hierarchical |
-------------------------------------+-------------------------------------
Comment (by hsyl20):
The discussion about the renaming has started on Phab. I'm copying it
here.
simonpj: For example, I'd like to remove the IR/ level, and just have Cmm,
Core etc. It doesn't pay its way in my view.
simonmar: I agree with @simonpj that IR should go away for example.
me:
Considering the proposed hierarchy, I have been loosely following the old
proposal on the wiki (ModuleDependencies/Hierarchical) but adapted it.
I have iterated quite a few times and indeed I started without the IR
level but it felt wrong for GHC.Haskell (isn't GHC all about Haskell?) and
GHC.Core ("core" is misleading and I wouldn't think it is an IR if I
wouldn't already know it is). Moreover I didn't want to pollute too much
the top-level.
In general I have tried to make module names meaningful and unambiguous,
even to someone that is first exposed to them. For instance, just by
looking at the outline (e.g., see current Haddock on
http://hsyl20.fr/ghc_doc/), even if we don't know what FloatOut is, we
know it's a transformation on Core IR.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/13009#comment:6>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list