#5125: SpecConstr messages should be reworded, and not be shown at standard
verbosity level
---------------------------------+------------------------------------------
    Reporter:  maltem            |       Owner:              
        Type:  bug               |      Status:  new         
    Priority:  normal            |   Component:  Compiler    
     Version:  7.0.3             |    Keywords:              
    Testcase:                    |   Blockedby:              
          Os:  Unknown/Multiple  |    Blocking:              
Architecture:  Unknown/Multiple  |     Failure:  None/Unknown
---------------------------------+------------------------------------------
 Currently GHC displays ''many'' messages about "specialisation over
 constructors" that typically look like this:

 {{{
 SpecConstr
     Function `$wks2{v s2dJ} [lid]'
       has one call pattern, but the limit is 0
     Use -fspec-constr-count=n to set the bound
     Use -dppr-debug to see specialisations
 }}}

 Some things are wrong with the design of this message:

 (1.) It is not apparent from the message if it is a fatal error, warning,
 or debug information. (End users who install the Haskell platform often
 think that something has gone wrong.)

 (2.) It is not apparent from the message that it is comes from the
 specialiser, unless you have read SpecConstr.lhs.

 (3.) The message is shown at standard verbosity, but it probably
 shouldn't.

 (4.) -fspec-constr-count is referenced, but not documented.

 See also #4288.

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