rust-lang / rust-lang/rust-analyzer
Cargo `build-dir` support
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
The Cargo team has done a Call for Testing for the unstable build-dir and I'm looking into stabilizing it. This allows users to move intermediate artifacts out of their target-dir. With how r-a is using target-dir (e.g. rust-lang/rust-analyzer#20072), it seems that build-dir will be the more appropriate location moving forward.
Note:
build-dirfiles do not have compatibility guarantees- In the future we may change the default
build-dir - In the future, we may change the layout of
build-dir
See https://github.com/rust-lang/cargo/issues/14125#issuecomment-2802967106
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
Start by tracing rust-analyzer's current use of target-dir and reviewing the Cargo build-dir proposal linked in the issue. Determine which intermediate artifacts are affected and what Cargo's compatibility and layout caveats mean for rust-analyzer; done should be defined as complete build-dir support, but the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100