#9117: Coercible constraint solver misses one -------------------------------------+------------------------------------ Reporter: goldfire | Owner: nomeata Type: bug | Status: new Priority: normal | Milestone: Component: Compiler | Version: 7.8.2 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: Unknown/Multiple Type of failure: None/Unknown | Difficulty: Unknown Test Case: | Blocked By: Blocking: | Related Tickets: -------------------------------------+------------------------------------ Comment (by nomeata): Yes, that’s a better example. So we have a dilemma: Should we support recursive newtypes better, or should we support different internal/external coercions better? Your trick in comment:13, shouldn’t that work for newtypes just as well? So maybe the original order was better after all... -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/9117#comment:22 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler