#1409: Allow recursively dependent modules transparently (without .hs-boot or
anything)
---------------------------------+------------------------------------------
Reporter: Isaac Dupree | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: _|_
Component: Compiler | Version: 6.10.2
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Os: Unknown/Multiple
Architecture: Unknown/Multiple |
---------------------------------+------------------------------------------
Comment (by augustss):
For me the reason to get rid of the -boot files is that each of them is
one more file.
One more file that duplicates information that occurs somewhere else, so
when I change something I have to change it in two places.
There are also build system complications (not so much when using ghc
--make), because there are new file types, new kinds of dependencies to
figure out etc., etc.
It just a medium pain, but enough of a pain that I sometimes go through
unnatural contorions just to avoid mutually recursive modules when it
would actually have been the natural solution.
I have an alternate design proposal:
Leave the pragma as is, i.e. SOURCE on some modules, but require an
explicit list of imports when using SOURCE. Also get rid of the -boot
file.
I can just about write a sed script that will generate the correct -boot
file from that information, so it feels like ghc might be able to do it
too.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1409#comment:16>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
