#7395: DefaultSignatures conflict with default implementations
----------------------------------+-----------------------------------------
    Reporter:  cgaebel            |       Owner:                           
        Type:  bug                |      Status:  new                      
    Priority:  normal             |   Milestone:                           
   Component:  Compiler           |     Version:  7.6.1                    
    Keywords:  DefaultSignatures  |          Os:  Unknown/Multiple         
Architecture:  Unknown/Multiple   |     Failure:  GHC rejects valid program
  Difficulty:  Unknown            |    Testcase:                           
   Blockedby:                     |    Blocking:                           
     Related:  7346               |  
----------------------------------+-----------------------------------------
Changes (by dreixel):

  * related:  => 7346


Comment:

 Replying to [comment:7 hvr]:
 > just a thought:
 >
 > ...what if the default-signature implementation would be only selectable
 by using the `deriving` facilities for auto-derivable classes?

 I can see the advantages, but there are also some problems. First, it only
 works if ALL the methods of the class have defaults (with signature or
 not). Second, when using normal deriving (not standalone) the compiler has
 to figure out the context for the instance, and this is not easy in
 general...

 See also #7346.

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