#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:22 simonpj]:
> "I absolutely hate it if I have to write a .hc-boot file" (I assume you
mean hs-boot file). I'm interested in identifying precisely what it is
that you hate, lest we fix the wrong thing:
>
> * Do you hate writing the type signatures of the functions that the
module exports? (After all, most Haskell programmers do that routinely.)
No, and I do it, too.
> * Do you hate putting those type signatures in a physically different
file? That is would the hate be alleviated if the signatures were in the
same file as the module implementation?
No; in fact sometimes I wish I could make module interfaces more explicit
a la ML or Modula.
> * Or perhaps you hate something else? Such as having to pick a place
to cut the recursive loop at all?
Yes. This is just distracting. Knowing that the compiler could do it
automatically, I don't like to do it manually.
Another point is that hc-boot files are non-standard.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1409#comment:28>
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
