#7748: Runtime <<loop>> due to incorrect inferred type
-----------------------------------------------------------------------+----
  Reporter:  jbransen                                                  |        
  Owner:                  
      Type:  bug                                                       |        
 Status:  closed          
  Priority:  normal                                                    |      
Milestone:                  
 Component:  Compiler (Type checker)                                   |        
Version:  7.6.2           
Resolution:  fixed                                                     |       
Keywords:                  
        Os:  Unknown/Multiple                                          |   
Architecture:  Unknown/Multiple
   Failure:  GHC accepts invalid program                               |     
Difficulty:  Unknown         
  Testcase:  typecheck/should_fail/T7748a, typecheck/should_run/T7748  |      
Blockedby:                  
  Blocking:                                                            |        
Related:                  
-----------------------------------------------------------------------+----

Comment(by maeder):

 I've attached a run of

 {{{
 #!/bin/bash -x

 ghc --version
 svn up
 svn st -q
 svn up -r 17856 Proofs/AbstractState.hs
 cabal clean
 cabal install -f "-programatica -server -gtkglade -haskeline -tar -hexpat"
 which hets
 hets ../Hets-lib/Datatypes.hpf

 export PATH=/local/maeder/ghc-7.6/bin:$PATH
 ghc-pkg list
 cabal install -f "-programatica -server -gtkglade -haskeline -tar -hexpat"
 hets ../Hets-lib/Datatypes.hpf
 }}}

 where /local/maeder/ghc-7.6 contains a local installation of
 ghc-7.6.2.20130416

 The <<loop>> only happens with ghc-7.6.2

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

_______________________________________________
ghc-tickets mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/ghc-tickets

Reply via email to