Project: simplification
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
We could simplify Rustup a lot. It was built with some very ambitious goals and it is clear that some of things will never happen, but the code is designed to accommodate them causing unnecessary complexity. It is also backwards compatible with very old versions of Rust and Rustup. There is lots of opportunity to reduce complexity. Some ideas:
- remove telemetry (this has never been used and is not that useful in any case)
- remove support for v1 manifests (we should still detect and error out with a message to delete things manually or whatever)
- support fewer ways to install Rust
- use standard logging rather than notifications
- merge some of the crates (probably only rustup and rustup-dist)
cc @rust-lang/cargo for any suggestions of things we should/should not do
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 breaking the proposal into the named areas: telemetry, v1 manifests, installation paths, notifications, and crate boundaries. Determine which simplifications are still wanted and define the compatibility and error-message expectations before changing code; done requires an agreed scope rather than implementing every idea listed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100