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

Add mode for continous parsing (not on-save) #402

Open
conjurationspellsoneone opened this issue Oct 19, 2024 · 1 comment
Open

Add mode for continous parsing (not on-save) #402

conjurationspellsoneone opened this issue Oct 19, 2024 · 1 comment

Comments

@conjurationspellsoneone
Copy link

conjurationspellsoneone commented Oct 19, 2024

One of the rough aspects of using scala over other languages like TypeScript is how sluggish it feels in the IDE, which I think is primarily due to Metal's not providing error detection / type analysis in real-time, instead requiring you to save the file every time.

And enabling interval auto-save for my IDE is also not a solution as I work in hot-reloaded contexts where I don't want to be distracted by broken code errors in the output half-way through, and also there are simply many contexts where this doesn't work.

For example
suppose function foo has 3 arguments, and I am in the middle of typing it, only provided one argument so far

if foo(bar.baz, 

but I am not quite sure if .baz is the right property on bar. I can't do ctrl + save yet, because I know for sure that the whole line will error because I am missing the next two arguments of foo. But until I ctrl + save, I won't know if bar.baz is an error.

In TypeScript an Python where syntax and type analysis is continuously provided on every keystroke, this is not an issue and it feels very fluid.

Regardless, this is a clear divide in preference among developers so supporting both is a good idea.

It would be great if you provided a setting flag to enable this method for the many developers who prefer it.

@tgodzik
Copy link
Contributor

tgodzik commented Oct 19, 2024

Thanks for reporting. Do you mean that you would want to see type errors from the compiler instead of only parsing error in metals?

I will move it to metals feature request as this repository really only deals with parsing

@tgodzik tgodzik transferred this issue from scalameta/scalameta Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants