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.

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

Refactor error reporting in TypeInference #78

Open
ppolesiuk opened this issue May 3, 2024 · 0 comments
Open

Refactor error reporting in TypeInference #78

ppolesiuk opened this issue May 3, 2024 · 0 comments
Labels
enhancement New feature or request error messages Improving error messages provided to the programmer

Comments

@ppolesiuk
Copy link
Member

Refactoring of error reporting is motivated by the following needs.

  • To solve the issue REPL pretty-printing based on toString method #19 we need to run the type-checker of find the instance of method toString. However, this could raise some type-errors, that should not be exposed to the user, or at least delayed until a proper message is displayed (about being unable to use toString method).
  • As suggested by @kwasielewski it would be nice to have good infrastructure for attaching notes to error messages.
  • We should set up the scene for managing warnings: being able to disable them or raise them to errors.
@ppolesiuk ppolesiuk added enhancement New feature or request error messages Improving error messages provided to the programmer labels May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request error messages Improving error messages provided to the programmer
Projects
None yet
Development

No branches or pull requests

1 participant