itsscb/rust-analyzer
1
0
Fork 0
mirror of https://github.com/rust-lang/rust-analyzer.git synced 2025-09-28 11:20:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #20638 from Kobzol/book-share-cache

Browse Source 
Add a FAQ entry about RA and Cargo build lock/cache conflicts
This commit is contained in:
Chayim Refael Friedman 2025-09-09 07:25:56 +00:00 committed by GitHub
commit a61c419024
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/book/README.md
View File

@ -8,6 +8,7 @@ To run the documentation site locally:
```shell
cargo install mdbook
cargo install mdbook-toc
cargo xtask codegen
cd docs/book
mdbook serve

9
docs/book/src/faq.md
View File

@ -5,3 +5,12 @@
rust-analyzer fails to resolve `None`, and thinks you are binding to a variable
named `None`. That's usually a sign of a corrupted sysroot. Try removing and re-installing
it: `rustup component remove rust-src` then `rustup component install rust-src`.
### Rust Analyzer and Cargo compete over the build lock
Rust Analyzer invokes Cargo in the background, and it can thus block manually executed
`cargo` commands from making progress (or vice-versa). In some cases, this can also cause
unnecessary recompilations caused by cache thrashing. To avoid this, you can configure
Rust Analyzer to use a [different target directory](./configuration.md#cargo.targetDir).
This will allow both the IDE and Cargo to make progress independently, at the cost of
increased disk space usage caused by the duplicated artifact directories.