bjorn3
commented
2 years ago One example is that by default, cargo check is run after every save and it checks all of my dependencies.
That sounds like the build cache is constantly being invalidated. Do you run cargo in the terminal too? Can you check if RUSTFLAGS is identical between rust-analyzer and the cargo you run from the terminal?
It seems like this is all metadata which should be cached accross sessions aswell.
Duplicate of https://github.com/rust-analyzer/rust-analyzer/issues/4712
therealdannzor
kornelski
lnicola
jonas-schievink
matklad
mankinskin
I use the vscode plugin.
One example is that by default, cargo check is run after every save and it checks all of my dependencies. This has led me to run low on RAM a couple of times and it was a headache to figure out how to fix it. The defaults should definitely prioritize perfomance more in my opinion, even if it means not showing off all features from the start. It is a much better experience to find things you can enable than having to figure out stuff you don't need because its annoying you.
One example is to use
cargo check --workspaceby default, because this is the only code that actually changes. Any dependency infomation should be cached and reused. One problem I haven't figured out yet is how to stop rust-analyzer from "indexing" 2000 packages (including standard libaries) every time I open my project. It seems like this is all metadata which should be cached accross sessions aswell.