matthiaskrgr / matthiaskrgr/cargo-cache
Cargo `build-dir` support
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 994
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
The Cargo team has started a Call for Testing for build-dir which allows users to move intermediate artifacts out of their target-dir. This may break affect the behavior of cargo cache and I would recommend testing this feature out to identify if it does so you can prepare for when your users start using it (or for the future possibilities below), including
- Preparing any new workarounds.
- Identifying use cases not yet considered for
-Zgc
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
No contributing guide indexed for this repository
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 testing Cargo's build-dir feature with cargo-cache and compare how intermediate artifacts are handled relative to target-dir. Check the linked Cargo issue for the feature context, then document any broken behavior, needed workarounds, or relevant -Zgc use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100