[GHC] #9256: Support automatic derivation of an hs-boot file from an hs file

[GHC]

#9256: Support automatic derivation of an hs-boot file from an hs file
-------------------------------------+------------------------------------
        Reporter:  ezyang            |            Owner:  ezyang
            Type:  feature request   |           Status:  new
        Priority:  normal            |        Milestone:
       Component:  Compiler          |          Version:  7.8.2
      Resolution:                    |         Keywords:  backpack
Operating System:  Unknown/Multiple  |     Architecture:  Unknown/Multiple
 Type of failure:  None/Unknown      |       Difficulty:  Unknown
       Test Case:                    |       Blocked By:
        Blocking:                    |  Related Tickets:
-------------------------------------+------------------------------------

Comment (by goldfire):

 Don't let this hold you up, but I can't really understand the proposal
 above.

 Where is augustss's proposal in #1409? There's ''lots'' of text there.

 What is a "mutual recursion breaker"? Is it something that ''does'' appear
 in the hi-boot file? Or is it something that ''does not'' appear in the
 hi-boot file? (Sounds like the latter.)

 Are you proposing that every module, even in the absence of pragmas, now
 produce both a hi and a hi-boot file?

 Your proposal suggests that every top-level definition will now need a
 type signature, but I don't imagine you mean that. Is this only when some
 pragma is specified?

 Then, not quite understanding what breakers are, my understanding goes
 downhill from there.

 In your summary, is there something that distinguishes a "hs to hs-boot
 file" from a normal hs file?

 Sorry -- this is interesting to me, but I'm a little lost here. Thanks!

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/9256#comment:3>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler