Specialized type hints
Simon Peyton Jones
simonpj at microsoft.com
Fri Mar 4 10:25:58 UTC 2016
Improving error message is an excellent goal, and one that I have spent more hours on than I care to tell you.
If you have a particular one in mind, could you open a Trac ticket with a particular reproducible test case, the error message you get, and the error message you’d like to get.
From: ghc-devs [mailto:ghc-devs-bounces at haskell.org] On Behalf Of Christopher Allen
Sent: 03 March 2016 07:55
To: ghc-devs at haskell.org
Subject: Specialized type hints
I'd like to see how warm people would be to catching GHC's type error quality up a bit.
I did a write-up on a confusion a reader of our book had:
This is not new. A lot of people complain about this particular type error in particular when they say GHC has bad type errors. I don't think GHC's type errors are bad, but I do think they could be improved and this particular issue has an unfortunate source to sink distance.
I would rather type error improvements not be buried behind a "silly beginners only" flag and that they just be part of improving the UX for everyone. With that proviso, how likely would specialized type error hints and some general error message fix ups be regarded?
By specialized I mean, "detect that they tried to find an instance of Num for (-> something something) and suggest that they did the wrong thing, with possible fixes: X Y Z". Ideally before the "hey do you want FlexibleContexts?!" thing fires.
I do not think I am capable of doing this, but being able to zoom in, clang style, to the expression where they are (probably accidentally) using a function like a Num or a Num like a function would be pretty valuable so they don't have to guess-n-check parenthesize their code.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ghc-devs