fix(cli/rustup-mode)!: change rustup doc --error_codes to --error-codes#4142
Merged
rami3l merged 1 commit intorust-lang:masterfrom Jan 4, 2025
Merged
fix(cli/rustup-mode)!: change rustup doc --error_codes to --error-codes#4142rami3l merged 1 commit intorust-lang:masterfrom
rustup doc --error_codes to --error-codes#4142rami3l merged 1 commit intorust-lang:masterfrom
Conversation
djc
approved these changes
Jan 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a pre-existing upstream issue (the naming of the directory is not following the convention: it should be
error-codes/index.htmlinstead oferror_codes/index.html), but I think on our side--error-codesshould be better.The only exception here is
--proc_macro, and I don't think it should ever been changed since it's really an entire Rust idiom instead of several words concatenated by word connectors.PS: Regarding backwards compatibility, this new flag was introduced in v1.28.0 beta, so it'd be fine to break it.