[GHC] #14319: Stuck type families can lead to lousy error messages
GHC
ghc-devs at haskell.org
Fri Oct 6 02:58:30 UTC 2017
#14319: Stuck type families can lead to lousy error messages
-------------------------------------+-------------------------------------
Reporter: dfeuer | Owner: (none)
Type: bug | Status: new
Priority: normal | Milestone: 8.4.1
Component: Compiler (Type | Version: 8.3
checker) | Keywords: TypeInType,
Resolution: | TypeFamilies
Operating System: Unknown/Multiple | Architecture:
Type of failure: Poor/confusing | Unknown/Multiple
error message | Test Case:
Blocked By: | Blocking:
Related Tickets: | Differential Rev(s):
Wiki Page: |
-------------------------------------+-------------------------------------
Comment (by goldfire):
While I agree that these error messages are perhaps misleading, I argue
that we should protect the common case from erosion. What I mean here is
that the vast majority of these kinds of errors are, I'm sure, places
where arities ''are'' known, and I would want to continue to report those.
I would even want to do this if, sometimes, an error message is a bit
wrong -- the cognoscenti that write the code leading to the error messages
will know better, anyway.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/14319#comment:3>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list