Allow specifying multiple toolchains in `rust-toolchain.toml` file, with first as default, with auto-installation for all.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Problem you are trying to solve
When running a project, often times, one wants to use nightly features from rustfmt, while also keeping a stable version for builds + deploys.
Solution you'd like
Allow a second key called [[other-toolchain]] to specify non-default toolchains. This should be backwards-compatible with the current rust-toolchain format:
# this is for builds
[toolchain]
channel = "1.70.0"
targets = [ "wasm32-unknown-unknown", "aarch64-linux-android" ]
# this is for rustfmt
[[other-toolchain]]
channel = "nightly-2023-11-26"
Notes
No response
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 by tracing how rustup currently reads and applies rust-toolchain.toml, using the existing [toolchain] format as the baseline. Define how [[other-toolchain]] entries should be parsed, installed, and kept backward-compatible, then add coverage for a default toolchain plus multiple additional toolchains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100