#13009: Hierarchical Module Structure for GHC -------------------------------------+------------------------------------- Reporter: hsyl20 | Owner: hsyl20 Type: task | Status: patch Priority: low | Milestone: Component: GHC API | 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 mpickering): I think the benefits of this are very marginal and the costs quite high for package maintainers. In general I don't like long module names but that is also a matter of preference. It is usual (at least in my projects) to import modules from GHC as qualified which avoids the problem with clashing module names. To take your example of `FloatOut`, it's already in the folder called `simplCore`. The modules are organised in a directory hierarchy just not a namespace hierarchy. It seems the benefit is for browsing documentation in haddock, but it is already hard to use haddock with GHC as not that many functions have haddock comments and you need to read the Notes in order to understand everything. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/13009#comment:10 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler