#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  |  
---------------------------------+------------------------------------------
Changes (by guest):

 * cc: i...@isaac.cedarswampstudios.org (added)
  * os:  Linux => Unknown/Multiple
  * architecture:  x86 => Unknown/Multiple

Comment:

 (affects all os/arch.)  I'm still interested, although more cautiously so
 than when I reported it.  Simon's point about "module signatures" could go
 along with work that essentially integrates hs-boot information into a .hs
 file (and is worthy work on its own).  My wish that multiple modules could
 be compiled in one unit is complicated quite a bit more than I suggested
 in the description, by the many per-module language extensions that
 sometimes change semantics in a conflicting way (and reducing the amount
 of arbitrarily per-module / per-typechecking-unit extension stuff in some
 way, might be a good thing on its own too).
 -Isaac Dupree

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1409#comment:12>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to