#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 guest):
Replying to [comment:16 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 agree, Why need another file to contain those information? Why GHC can't
pick-up those information through analysis source file?
Maybe it's a hard work to GHC developer, but i think it's worth to do.
It's not problem just write .hs-boot file, it's not too hard to write .hs-
boot file.
But Haskell programmer will spend too *much* time to synchronous
information between .hs file and .hs-boot file, and special to *big*
project.
And i think the *natural* way is GHC do those work automatically. Then
save time and less problem (bug).
-- Andy
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1409#comment:19>
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
