#1595: duplicate "not in scope" error when giving multiple vars type-signatures 
at
once
---------------------------------+------------------------------------------
    Reporter:  Isaac Dupree      |        Owner:  michalt                       
   
        Type:  bug               |       Status:  patch                         
   
    Priority:  normal            |    Milestone:  _|_                           
   
   Component:  Compiler          |      Version:  6.6.1                         
   
    Keywords:                    |     Testcase:                                
   
   Blockedby:                    |   Difficulty:  Unknown                       
   
          Os:  Unknown/Multiple  |     Blocking:                                
   
Architecture:  Unknown/Multiple  |      Failure:  Incorrect warning at 
compile-time
---------------------------------+------------------------------------------
Changes (by simonpj):

 * cc: david.waern@… (added)


Comment:

 Thank you Michael!  Can you make a testsuite test or two as well? Did you
 validate?

 '''David, Simon M''': I'm happy with the GHC changes but I'm not qualified
 to review the Haddock patch, but I expect it is fine.  The change is that
 instead of `HsBinds.Sig` being defined like this:
 {{{
 data Sig name
   = TypeSig (Located name) (LHsType name)
   | ...other constructors..
 }}}
 it takes a ''list'' of names, thus
 {{{
 data Sig name
   = TypeSig [Located name] (LHsType name)
   | ...other constructors..
 }}}
 thus making `HsSyn` reflect exactly the Haskell source syntax
 {{{
 f,g :: Int
 }}}
 The changes to Haddock are simply to follow this representation change.

 Michael has left a few FIXME comments, all relating to "can I just pick
 the first name from the list".

 Would you like to review?  If I don't hear otherwise I'll just commit in a
 couple of weeks.

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1595#comment:10>
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

Reply via email to