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

analyzing in not-saved file #14699

Closed
hvlxh opened this issue May 1, 2023 · 5 comments
Closed

analyzing in not-saved file #14699

hvlxh opened this issue May 1, 2023 · 5 comments
Labels
C-feature Category: feature request

Comments

@hvlxh
Copy link

hvlxh commented May 1, 2023

the errors are shown when the file was saved, it is good receiving the errros when we changing than receiving the errors after saving it and have to fix them again!
Record_2023_05_01_17_17_07_79

@hvlxh hvlxh added the C-feature Category: feature request label May 1, 2023
@hvlxh
Copy link
Author

hvlxh commented May 1, 2023

also the errors stay up even if i fixed it until i saved the file

@lnicola
Copy link
Member

lnicola commented May 1, 2023

We can't update those without running cargo check, and we only run it on save. You can set up auto-saving, but it's usually not worth the trouble.

@hvlxh
Copy link
Author

hvlxh commented May 1, 2023

auto-save? i think that's an good alternative solution for this issue, thanks!

@hvlxh hvlxh closed this as completed May 1, 2023
@hvlxh
Copy link
Author

hvlxh commented May 1, 2023

wait i am still opening this though, there is no problem with that alternative solution too.

I am pretty sure vscode can give the current changes even if it is not saved. so you can use cargo check with gained code and show the result!

@hvlxh hvlxh reopened this May 1, 2023
@lnicola
Copy link
Member

lnicola commented May 1, 2023

We have our own diagnostics (the more interesting ones disabled by default) that run when typing. But we don't want to run cargo check on every keystroke: #3107.

@hvlxh hvlxh closed this as completed May 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature Category: feature request
Projects
None yet
Development

No branches or pull requests

2 participants