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

Type errors aren't easy to read #85

Open
nasso opened this issue Mar 7, 2022 · 0 comments
Open

Type errors aren't easy to read #85

nasso opened this issue Mar 7, 2022 · 0 comments
Labels
A-analyser Area: analyser A-parser Area: parser enhancement New feature or request

Comments

@nasso
Copy link
Owner

nasso commented Mar 7, 2022

Right now, errors emitted by the type-checker are simply printed using their Show instance. This is "cringe".

We should provide information about the file, line, and syntactic constructs related to the error. It would be even better to show more context and help/suggestions that can better explain what is wrong with the code.

Currently, the AST does not store any information about the location of the tokens in the source code. This is required to produce error messages after parsing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-analyser Area: analyser A-parser Area: parser enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nasso