#6028: warning for cyclic unimplemented defaults
-------------------------------+--------------------------------------------
Reporter: lerkok | Owner:
Type: feature request | Status: closed
Priority: normal | Milestone:
Component: Compiler | Version: 7.4.1
Resolution: wontfix | Keywords:
Os: Unknown/Multiple | Architecture: Unknown/Multiple
Failure: None/Unknown | Difficulty: Unknown
Testcase: | Blockedby:
Blocking: | Related:
-------------------------------+--------------------------------------------
Comment(by lerkok):
It is indeed possible to create scenarios where the "cycle" check would be
fooled, like the one you showed above. But I don't think that's the
"common case". I believe it remains a fact that a simply cycle check will
catch a large number of practical instances of this problem. This is
similar to the pattern-match completeness warning: While it may not be
accurate 100%, it's so darn useful. And it's likely to be right more often
than you'd think. In the 1% of cases where it's wrong, it's just a warning
that the user can explicitly turn off via
`--noWarnUnimplementedCyclicMethod` or some such.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/6028#comment:4>
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
