-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spelling #110392
Spelling #110392
Conversation
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
This PR is pretty big.. Would it be easy to split these changes into smaller PRs? |
The job Click to see the possible cause of the failure (guessed by this bot)
|
You should also squash the commits afterward the splitting up (the best way to split it up is probably after specific areas (compiler, library, rustdoc etc). With the tests you should be careful and maybe avoid them for now to not accidentally make the test wrong. Changes to rustc_codegen_gcc, rustc_codegen_cranelift, clippy, cargo and rustfmt should be filed on their respective repositories instead of here. |
There are several problems with this PR:
Per #58619 and precedent for large "typo fixes" PRs, I'm going to close this. Thanks for your contribution to rustc. |
I assume that typo fixing was automated using a tool, and I'd have no problem with typos being fixed for ui tests. I totally agree that it should be split into different subfolders only ( On another note, we can have bors squash the commits before merging so having each commit for each word is not a really big problem (except for being hard to navigate as a reviewer because I would have to click on each commit to see the changes). |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I won't finish the annotations, but here's what I had when I stopped...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some projects don't like changing changelogs. Happy to drop.
// poision "2*precision - 1" to "precision - 1". The exponent need to be | ||
// poisson "2*precision - 1" to "precision - 1". The exponent need to be |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
Alternatively you can download a pre built version from [Github Actions]. It is listed in the artifacts section | ||
Alternatively you can download a pre built version from [GitHub Actions]. It is listed in the artifacts section |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
brand
// The following is a work around that replaces `pub mod llvm;` and that fixes issue 53912. | ||
// The following is a workaround that replaces `pub mod llvm;` and that fixes issue 53912. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the noun form is a single word.
/// A way to temporarily opt out of opt in copy. This will *never* be accepted. | ||
/// A way to temporarily opt out of opt-in copy. This will *never* be accepted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nouns compound with either -
or without a space, verb phrases don't compound. Here, opt out
is a verb phrase, whereas opt-in
is the noun.
// get all where BoundPredicates here, because they are used in to cases below | ||
// get all where BoundPredicates here, because they are used in two cases below |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, I do not check 2-letter words. Here, in to
tripped a check and it appears that to
was the wrong homonym.
// can't add `#[rustc_clean]` etc without opting in to this feature | ||
// can't add `#[rustc_clean]` etc without opting into this feature |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should note that in to
/into
changes to be quite controversial. I'm happy to drop them (or anything else).
infer_prlf_must_oultive_with_sup = ...must outlive the lifetime `{$sup_symbol}` defined here | ||
infer_prlf_must_oultive_without_sup = ...must outlive the lifetime defined here | ||
infer_prlf_must_outlive_with_sup = ...must outlive the lifetime `{$sup_symbol}` defined here | ||
infer_prlf_must_outlive_without_sup = ...must outlive the lifetime defined here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-oultive
+outlive
infer_oc_intristic_correct_type = intrinsic has wrong type | ||
infer_oc_intrinsic_correct_type = intrinsic has wrong type |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-intristic
+intrinsic
if let ty::ConstKind::Bound(debrujin, b) = result_value.kind() { | ||
if let ty::ConstKind::Bound(debruijn, b) = result_value.kind() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These two tokens were adjacent in the word list and one appeared dominant.
Sorry, we cannot actually rely on bors to do squashing. |
I'm quite happy to do the squashing, can someone suggest a limited subset of directories they'd like me to start w/? I'm fully capable of doing splits and squashes, but I do need direction. If there's a specific set of directories I should absolutely ignore, I can take that now and drop changes to them. |
rustc_apfloat needs to be ignored. I'd recommend splitting as I described above. You can |
Yeah.. sorry for forgetting about that. |
…iddle Spelling librustdoc This is split from rust-lang#110392 There's one change to src/tools/rustdoc-gui/tester.js which feels like a reasonable thing to piggy-back here.
Spelling compiler This is per rust-lang#110392 (comment) I'm going to delay performing a squash because I really don't expect people to be perfectly happy w/ my changes, I really am a human and I really do make mistakes. r? Nilstrieb I'm going to be flying this evening, but I should be able to squash / respond to reviews w/in a day or two. I tried to be careful about dropping changes to `tests`, afaict only two files had changes that were likely related to the changes for a given commit (this is where not having eagerly squashed should have given me an advantage), but, that said, picking things apart can be error prone.
…lbertlarsan68 Spelling src bootstrap The various src/* items seem slightly disparate, so I'm doing src/* individually. split from rust-lang#110392
…rsan68 Spelling src ci The various src/* items seem slightly disparate, so I'm doing src/* individually. split from rust-lang#110392
…lacrum Spelling src etc The various src/* items seem slightly disparate, so I'm doing src/* individually. split from rust-lang#110392
Spelling src etc The various src/* items seem slightly disparate, so I'm doing src/* individually. split from rust-lang/rust#110392
Spelling rustdoc Split per rust-lang#110392 (comment)
Spelling library Split per rust-lang#110392 I can squash once people are happy w/ the changes. It's really uncommon for large sets of changes to be perfectly acceptable w/o at least some changes. I probably won't have time to respond until tomorrow or the next day
Spelling library Split per rust-lang/rust#110392 I can squash once people are happy w/ the changes. It's really uncommon for large sets of changes to be perfectly acceptable w/o at least some changes. I probably won't have time to respond until tomorrow or the next day
This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at https://github.com/jsoref/rust/actions/runs/4712066890#summary-12779316921
The action reports that the changes in this PR would make it happy: https://github.com/jsoref/rust/actions/runs/4712067124#summary-12779317247