Skip to content

Explore reporting syntax errors as you type. #448

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

Closed
cristianoc opened this issue Jun 2, 2022 · 4 comments
Closed

Explore reporting syntax errors as you type. #448

cristianoc opened this issue Jun 2, 2022 · 4 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@cristianoc
Copy link
Collaborator

The parser is vendored in the extension and is always available. Does not need to wait for type information.
Explore reporting syntax errors for unsaved code.

This should be fast enough to feel responsive, but not so fast that it gets in the way and produce noise while you type.

@zth
Copy link
Collaborator

zth commented Jun 6, 2022

For anyone interested in this, it's a good idea to get a feel for what for example TS and Rust does in this regard. We don't have to copy them, but it'll probably be a good guide for what direction to take.

@zth zth added enhancement New feature or request help wanted Extra attention is needed labels Jun 6, 2022
@aspeddro
Copy link
Contributor

Is it possible to also catch type errors with parser?

@cristianoc
Copy link
Collaborator Author

cristianoc commented Jun 15, 2022

No when the parser runs, the type checker has not run yet.

@zth
Copy link
Collaborator

zth commented Jul 8, 2022

This is done in #457

@zth zth closed this as completed Jul 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants