rust-lang / rust-lang/cargo-bisect-rustc
warn if absolute path to rustc is used
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 206
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
I recently ran into an interesting™ situation where I passed an absolute rustc path into CBR, like --script=/home/matthias.../.rustup/.../rustc
This prevents cbr from being able to dynamically alter the RUSTC version used (I guess) since rustc is no longer gotten through the the rustup wrapper or whatever, meaning that cbd will potentially download an infinite number of nightlies because it never finds a change in rustc $file behaviour because the rustc used is always the same 😆
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 tracing how the --script argument and rustc path are handled. Add a warning for an absolute rustc path, then verify that the warning appears for the reported absolute-path case and does not trigger for a normal command name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100