rust-lang / rust-lang/rust-analyzer
Excluding a crate from analysis?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Is there a way to exclude a single crate from analysis?
I've got a dependency in my project that takes too much time to analyze (about 5-10 minutes on ryzen 7 2700) due to a really large amount of proc-macro generated code in it, and since there's no persistent cache in rust-analyzer, every time I reopen the project I have to wait for quite some time for the whole thing to be processed. On the other hand, it's not like I can definitely live without types/completion from that crate..
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file, test, or entry point. Start by checking whether existing rust-analyzer configuration supports excluding one dependency while retaining its types and completion; done means a documented, usable way to make that trade-off.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100