Rust and Git worktrees: share one Cargo build
Comments on “Rust and Git worktrees: share one Cargo build”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
DocSpring describes sharing one Cargo build directory across git worktrees without one worktree running another's code. It sets build.build-dir and adds a per-worktree --cfg flag to workspace crates through unstable profile rustflags, so only dependencies are shared. On the author's Lambda workers, later worktrees need 2.7 GB and 22 seconds instead of 8.2 GB and 99 seconds, and ten worktrees take 33 GB instead of 82 GB. The figures are self-measured on one laptop, and the setup depends on an unsupported nightly override. DocSpring has since replaced it with kache.
Why it ranked
No. 14 of 60 with a score of 0.64. The panel rated it highest on technical depth (0.93) and substantiated (0.91), lowest on audience breadth (0.43). Placed No. 14, No. 20 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Detailed, well-evidenced engineering write-up on Cargo build sharing across git worktrees with reproducible measurements; useful to Rust builders but narrow in audience and not a landmark.
- AI judgeJudge 3gpt-5.6-luna
- A detailed, measured Cargo/worktree engineering solution with reproducible configuration, failure modes, concurrency caveats, and substantial disk/time improvements. It is highly actionable for Rust teams, though narrower than general tech and depends on unstable Cargo features.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.64total under rubric v2.3
- Significance0.46
- Reader interest0.71
- Audience breadth0.43
- Practical relevance0.80
- Substantiated0.91
- Technical depth0.93
- New information0.82
- Counts against: Promotional0.04
- Counts against: Overclaim0.14
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.48 | 0.35 | 0.55 | 0.46 | 0.20 | +0.24 | +0.111 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.60 | 0.72 | 0.82 | 0.71 | 0.22 | +0.26 | +0.185 |
| Audience breadthHow many people who build technology does it concern? | 0.43 | 0.42 | 0.45 | 0.43 | 0.03 | +0.13 | +0.056 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.84 | 0.70 | 0.85 | 0.80 | 0.15 | +0.22 | +0.176 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.98 | 0.85 | 0.90 | 0.91 | 0.13 | +0.05 | +0.046 |
| Technical depthHow technically substantive is it? | 1.00 | 0.90 | 0.90 | 0.93 | 0.10 | +0.05 | +0.047 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.89 | 0.60 | 0.98 | 0.82 | 0.38 | +0.05 | +0.041 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.03 | 0.05 | 0.03 | 0.04 | 0.02 | −0.19 | −0.007 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.18 | 0.15 | 0.08 | 0.14 | 0.10 | −0.11 | −0.015 |
| Sum of contributions | +0.639 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.639 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-16/14/"><img src="https://rubric.hrih.si/badge/2026-11-16/14.svg" alt="Ranked #14 on Rubric, 16 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 1 matches source · 4 no source given · 3 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkDate
Cargo has had an open issue since 2023 about two worktrees of the same repository producing the same hash for workspace crates.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Cargo has had an open issue for this since 2023”
The source says No passage could be compared.
Source cited by the article: github.com/rust-lang/cargo/issues/12516
Couldn’t checkCausal conclusion
Cargo's fine-grained locking can deadlock when two builds start together, and the Cargo team member working on it says the design isn't sound yet.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “two builds that start together can deadlock, each waiting for a unit the other one has locked, and the Cargo team member working on it says the design isn't sound…”
The source says No passage could be compared.
Source cited by the article: github.com/rust-lang/cargo/issues/17508
No source givenNumber
In two days, about ten worktrees built the workers and their build folders grew from 11 GB to about 80 GB.
The article gives no link or citation for it.
The article says “In two days, about ten worktrees built the workers, and their build folders went from 11 GB to about 80 GB”
The source says No source to compare with.
No source givenNumber
With a shared build directory, each worktree after the first takes 2.7 GB and 22 seconds versus 8.2 GB and 99 seconds with separate build folders.
The article gives no link or citation for it.
The article says “Each worktree after that 8.2 GB, 99 seconds 2.7 GB, 22 seconds”
The source says No source to compare with.
No source givenNumber
Ten worktrees take 82 GB with separate build folders and 33 GB with a shared build directory.
The article gives no link or citation for it.
The article says “Ten worktrees 82 GB 33 GB”
The source says No source to compare with.
No source givenVersion
Cargo's build.build-dir setting is available since Cargo 1.91.
The article gives no link or citation for it.
The article says “since Cargo 1.91, with the build.build-dir setting”
The source says No source to compare with.
Couldn’t checkCausal conclusion
sccache skips incremental builds and any crate that runs the linker, so it cannot cache the workspace's own crates.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “sccache skips incremental builds, as well as any crate that runs the linker (binaries and proc macros”
The source says No passage could be compared.
Source cited by the article: github.com/mozilla/sccache
Matches sourceDate
A Cargo build cache shared between workspaces is one of the Rust project's goals for 2026, starting with a nightly prototype for simple crates.
The cited source says the same thing.
The article says “it's one of the Rust project's goals for 2026. The plan starts with a nightly prototype for simple crates”
The source says “Cargo cross workspace cache | Ross Sullivan | cargo | Ed Page”
Source cited by the article: goals.rust-lang.org/2026/goals.html
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 3 pts, not on front page
Recorded for context only, checked 16 Nov 2026, 05:47 UTC. It played no part in the ranking.