-
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 compiler #110417
Spelling compiler #110417
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Nilstrieb (or someone else) soon. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
This PR changes MIR cc @oli-obk, @RalfJung, @JakobDegen, @davidtwco, @celinval, @vakaras Some changes occurred in cc @BoxyUwU Some changes occurred in need_type_info.rs cc @lcnr Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri Some changes occurred to the core trait solver cc @rust-lang/initiative-trait-system-refactor Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt Some changes occurred in cc @BoxyUwU Changes rustc_apfloat. rustc_apfloat is currently in limbo and you almost certainly don't want to change it (see #55993). cc @eddyb These commits modify compiler targets. Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri |
I will review this once CI passes. Looks like some functions got renamed but not everywhere. |
This comment has been minimized.
This comment has been minimized.
tests/ui/type-alias-enum-variants/enum-variant-generic-args.stderr
Outdated
Show resolved
Hide resolved
d845f82
to
b7db808
Compare
This comment has been minimized.
This comment has been minimized.
This |
b7db808
to
9094fbf
Compare
This comment has been minimized.
This comment has been minimized.
9094fbf
to
991385e
Compare
I've hit that ordering thing a couple of times and I thought I fixed it a couple of times. It's taken me a while to understand why it's happening (because I see the beginning word and treat it as if it's the same for both of the first two tokens, but, of course by fixing the spelling of the beginning word) -- the second word now sorts properly instead of jumping the queue because it was sorting against the last letter of the previous word. |
991385e
to
19a3cb3
Compare
@@ -22,7 +22,7 @@ pub(crate) struct UnderscoreLifetimeNameCannotBeUsedHere(#[primary_span] pub(cra | |||
|
|||
#[derive(Diagnostic)] | |||
#[diag(resolve_crate_may_not_be_imported)] | |||
pub(crate) struct CrateMayNotBeImprted(#[primary_span] pub(crate) Span); | |||
pub(crate) struct CrateMayNotBeImported(#[primary_span] pub(crate) Span); |
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.
This struct is dead code, no one mentions it. You shouldn't remove it here, but this is interesting anyways. Looks like something from the diagnostics derive is messing up the dead code lint (cc @davidtwco).
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.
r=me after squashing
19a3cb3
to
336a285
Compare
☔ The latest upstream changes (presumably #110458) made this pull request unmergeable. Please resolve the merge conflicts. |
* account * achieved * advising * always * ambiguous * analysis * annotations * appropriate * build * candidates * cascading * category * character * clarification * compound * conceptually * constituent * consts * convenience * corresponds * debruijn * debug * debugable * debuggable * deterministic * discriminant * display * documentation * doesn't * ellipsis * erroneous * evaluability * evaluate * evaluation * explicitly * fallible * fulfill * getting * has * highlighting * illustrative * imported * incompatible * infringing * initialized * into * intrinsic * introduced * javascript * liveness * metadata * monomorphization * nonexistent * nontrivial * obligation * obligations * offset * opaque * opportunities * opt-in * outlive * overlapping * paragraph * parentheses * poisson * precisely * predecessors * predicates * preexisting * propagated * really * reentrant * referent * responsibility * rustonomicon * shortcircuit * simplifiable * simplifications * specify * stabilized * structurally * suggestibility * translatable * transmuting * two * unclosed * uninhabited * visibility * volatile * workaround Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
336a285
to
e09d0d2
Compare
@bors r+ |
…llaumeGomez Rollup of 5 pull requests Successful merges: - rust-lang#110417 (Spelling compiler) - rust-lang#110441 (5 little typos) - rust-lang#110485 (Fix bootstrap locking) - rust-lang#110488 (Add a failing rustdoc-ui test for public infinite recursive type) - rust-lang#110490 (Bump `download-ci-llvm-stamp` for loong support) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
This is per #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.