Happy parse error messages should include more information
Open
- Dominant language
- Haskell
- Stars
- 322
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
Right now, parse errors include only the line number. For example:
```
Calc.ly:40: Parse error
```
It would be helpful to include a bit more easily accessible info:
* the token on which parsing failed
* the column position of that token
Contributor guide
Assessment
This issue has not been assessed yet.