Elm has a interesting take on this: a collection of all error messages (
https://github.com/elm-lang/error-message-catalog).
I created an empty repo (
https://github.com/bollu/hask-error-messages-catalog) and shot an email to
haskell-cafe asking for examples where GHC generates unintuitive error
m
This is a bit off topic, but is there a collection of not-so-great
error messages along with opinions about what they should be? Like a
wiki page or something?
I just stumbled across one and was going to complain, but didn't know
the most productive way to do that, aside from try to fix it myself
> On Jun 3, 2017, at 11:50 AM, Ben Gamari wrote:
>
> In particular, Richard Eisenberg
> advocated that error message documents look like,
>
>-- A dynamically typed value embedded in an error message
>data ErrItem = forall a. (Outputable a, Typeable a). ErrItem a
>
>type ErrDoc = Do
Hi,
Thanks for all the work on error messages, this is important.
Whatever you do please remember that not only humans are recipients of
these messages. Recently GHC changed 'Warning' into 'warning' and even that
caused some issues:
https://github.com/haskell/haskell-mode/issues/1513
2017-06-0
Alan & Kim Zimmerman writes:
> Thanks Ben, a great summary. Is there a Wiki page for this? It feels like
> it should be on one, so we can easily comment/update the individual points.
>
Here you are: https://ghc.haskell.org/trac/ghc/wiki/PrettyErrors
In the interest of time I essentially just pa
Thanks Ben, a great summary. Is there a Wiki page for this? It feels like
it should be on one, so we can easily comment/update the individual points.
In terms of the pretty-printer and its string type. Perhaps we could
backpackify it to use http://next.hackage.haskell.org:8080/package/str-sig,
an
CCing,
* Alfredo Di Napoli for his on-going work in this area
* Shivansh Rai for his interest in contributing
* David Luposchainsky for his recent pretty-printer library
* Richard Eisenberg due to his participation in #8809
* Bartosz for his participation in #10735
* Alan Zimmerm
Hello all,
Thanks for all the work that's put into GHC :)
I've tried to get into GHC development before, but I was unsuccessful,
mostly because I didn't dedicate enough time to understanding the problem
at hand & exploring the codebase.
I'd like to give it another shot. This time, I think I have
