I was using Iced as a dependency, but wanted to tweak its source code for some reason, so I jumped into the folder where cargo downloads dependencies, and went into iced_wgpu 13.5 (I think that’s the version).
I could make a change, then run
cargo clean -p iced_wgpu && cargo check
in my other project for instant feedback, yet it took rust_analyzer at least 5 whole minutes to stop hallucinating.
Can I disable some functionality of rust_analyzer? I only use it for jump-to-definition, linting and syntax highlighting; I don’t even use autocomplete.
Setup:
-
Desktop that thermally throttles only when both the IGPU and the CPU are under full load, and is cool otherwise.
-
CPU: Intel I5-7500
-
RAM: 8 GiB DDR-4
-
Editor: NVIM v0.11.0-dev | Build type: RelWithDebInfo | LuaJIT 2.1.0-beta3 (I had the same issue with other versions as well).
TLDR
What can I disable in rust_analyzer to boost performance while maintaining jump-to-definition, linting and syntax-highlighting, or what can I do to boost rust_analyzer for big projects in general?
Not related to your question at all, but:
I don’t recommend editing the source code from cargo’s files. Instead, the correct way to modify a dependency would be making a fork and using it as a gift dependency (or path dependency, which is even easier).