Skip to content

Rust-analyzer not works when switching workspaces in Vscode #5254

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
Edu4rdSHL opened this issue Jul 7, 2020 · 3 comments
Closed

Rust-analyzer not works when switching workspaces in Vscode #5254

Edu4rdSHL opened this issue Jul 7, 2020 · 3 comments
Labels
E-hard S-actionable Someone could pick this issue up and work on it right now

Comments

@Edu4rdSHL
Copy link

I have two different folders from different projects added to the workspace, when I works on the first one added RA works without problems but switching to the another project it just stop reporting problems. See #4894 for the actual behavior of RA when switching project folder.

In short, rust-analyzer doesn't show errors regarding to nonexistent or wrong typed variables, bad number of function parameters and more.

@matklad matklad added the E-hard label Jul 11, 2020
@Edu4rdSHL
Copy link
Author

Thanks, as workaround you can change the order of the folders and put in first place the one where you want to work, then restart vscode.

@lnicola lnicola added the S-actionable Someone could pick this issue up and work on it right now label Jan 18, 2021
@jonas-schievink
Copy link
Contributor

This is now fixed, we spawn one flycheck instance per client workspace

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-hard S-actionable Someone could pick this issue up and work on it right now
Projects
None yet
Development

No branches or pull requests

4 participants