Reproduction of a bad type error message #75
chrisdone-artificial
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@austin-artificial found this good repro example of a bad type error message.
The error is reported as if the
let
is in the wrong, when really the[env0, env1]
is where the conflicting types are happening.There's prior art for good error messages: HIW 2014: Lennart Augustsson: Better type-error messages - YouTube
But there might be more light-weight approaches, such as listing all unification errors, and not just stopping at the first.
Beta Was this translation helpful? Give feedback.
All reactions