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?

you are viewing a single comment's thread
view the rest of the comments

[–] SorteKanin@feddit.dk 2 points 1 year ago

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)

This is not the way you should be doing this. Do not edit cargo's downloaded source code, that's just wrong.

If you want to patch a dependency, use cargo's specific features for doing that.