Skip to content

feat(errors): suggest another toolchain on component removal - #5130

Merged
rami3l merged 2 commits into
rust-lang:mainfrom
devtechedge:component-rm-suggest-toolchain
Oct 7, 2026
Merged

rami3l merged 2 commits into
rust-lang:mainfrom
devtechedge:component-rm-suggest-toolchain

Conversation

@devtechedge

@devtechedge devtechedge commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Partially addresses: #5098

rustup component remove <component> now suggests another installed toolchain when the component isn't available in the current one. If no other toolchain has the component, the existing error is unchanged.

Same shape as #5094 for targets. The component add case is left for a follow-up.

@rami3l rami3l left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work and LGTM, thanks :)

View changes since this review

@rami3l

rami3l commented Oct 7, 2026

Copy link
Copy Markdown
Member

PS: I've changed your PR description so it no longer closes #5098 since it's not a full solution. I'll link this PR in the issue description afterwards.

@rami3l
rami3l added this pull request to the merge queue Oct 7, 2026
Merged via the queue into rust-lang:main with commit 4078bbb Oct 7, 2026
29 checks passed
@devtechedge

Copy link
Copy Markdown
Contributor Author

Thanks so much for the review and the merge, rami3l!

Splitting the panic fix out into its own PR was spot on, and it made this change much easier to reason about.

Mirroring the target hint from #5094 taught me a lot about how rustup shapes its error suggestions, and it was genuinely fun to work on.

Thanks also for fixing the description so #5098 stays open for the rest of the work 🦀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants