-
Notifications
You must be signed in to change notification settings - Fork 167
RLS/Clippy doesn't lint newly created files #921
Comments
Can you try https://marketplace.visualstudio.com/items?itemName=matklad.rust-analyzer instead (though it might be a bit finicky to set up in WSL -- you need to install it on the remote side and make sure everything is in |
Sure, I'll give that a shot! Will report back. |
Yes, if I disable the Rust extension and enable rust-analyzer instead, everything works as expected. Installing was easy by the way, no need to mess around with How does this extension compare to the "Rust" extension otherwise? |
See https://rust-analyzer.github.io/blog/2020/04/20/first-release.html and https://rust-lang.github.io/compiler-team/working-groups/rls-2.0/. It's supposed to replace RLS at some point, but it's currently developed outside of the Rust project.
Favourably, in my (biased, as a |
I'll still keep this issue open for now, as it seems relevant to the Rust extension. My first impression of |
You can disable most features, if that's what you mean, check out the manual or file an issue on that repo. In a sense, it does less since it delegates formatting (to |
Whenever I create a new .rs file in my project, I don't receive any warnings/lints until I restart VSCode. After I restart, everything works as expected.
I'm sure I must be doing something wrong; could someone help me out?
I am using VSCode through Windows Subsystem for Linux.
UPDATE: Including the file as a module in
lib.rs
fixes the issue. However, creating amain.rs
is still problematic, as this file is not included inlib.rs
.The text was updated successfully, but these errors were encountered: