rust-lang / rust-lang/cargo-bisect-rustc
leverage existing rustup nightlies
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 206
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
We could avoid network traffic (which to me seems like the big bottleneck, at least when one isn't using the --preserve flag to cargo-bisect-rustc) by looking at what nightlies the user has already installed via rustup, and first testing them before exploring versions that we would have to download from the CI service.
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 in cargo-bisect-rustc by tracing how nightly versions are selected and how versions are downloaded from the CI service. Check how rustup exposes already-installed nightlies and determine how the --preserve behavior fits into that flow. Done means installed nightlies are tested before versions that require network downloads, without losing the existing fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100