Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Analyzer] Improve type error reporting #314

Closed
Martinsos opened this issue Sep 24, 2021 · 1 comment
Closed

[Analyzer] Improve type error reporting #314

Martinsos opened this issue Sep 24, 2021 · 1 comment
Assignees
@Martinsos

Comments

@Martinsos
Copy link
Member

While we do report type errors right now in Analyzer, we report only first error we encounter and error messages are very raw + contain no context information (e.g. the position in the source code). We should improve this!

  1. Report multiple errors (by doing some kind of error recovery, e.g. putting a boundary at the lvl of statement / declaration).
  2. Report position of error in source code.
  3. Make user-readable messages for all errors, especially for unification/weaken errors since they are not that understandable.

TODO for this in TypeError.hs
@Martinsos Martinsos mentioned this issue Sep 24, 2021
Closed
8 tasks
@Martinsos Martinsos self-assigned this Dec 2, 2021
@Martinsos
Copy link
Member Author

Superseded by #385 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Martinsos Martinsos

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Martinsos