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

Improve developer experience and error messages #3

Open
3 tasks
yhyadev opened this issue Nov 6, 2024 · 0 comments
Open
3 tasks

Improve developer experience and error messages #3

yhyadev opened this issue Nov 6, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@yhyadev
Copy link
Contributor

yhyadev commented Nov 6, 2024

Why?

Status quo's error messages are barely helpful that it makes it easier for people to hate the language just by how the compiler communicate

How?

There are few tasks we need to achieve before this issue being closed:

  • Prefer to recover and not panic on one error message
  • Add helpful notes to show how should the user fix the error

Examples:

  1. Recommend to use .* suffix instead of prefix with *
  2. Recommend an available variable name to use instead of undeclared one (same for fields), which requires some autocorrection techniques and using the scope as the dictionary
  • Print what did the compiler see to get that error
@yhyadev yhyadev added the enhancement New feature or request label Nov 6, 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
Projects
None yet
Development

No branches or pull requests

1 participant