add `--explain` or `--verbose` option to `rustup which`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
I would love if there were a way to have rustup which tell me why it had selected a particular tool. I imagine rustup which --explain rustc or something like that, which would show all of the relevant overrides (or at least the override that was used in this case).
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 with the rustup which command and trace how it selects a toolchain and applies overrides. Define how an --explain or --verbose option should present the relevant overrides, then verify that rustup which --explain rustc identifies why the selected tool was chosen.
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