Spelling compiler

[jsoref]

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.

[rustbot]

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 (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[rustbot]

This PR changes MIR

cc @oli-obk, @RalfJung, @JakobDegen, @davidtwco, @celinval, @vakaras

Some changes occurred in abstract_const.rs

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 const_evaluatable.rs

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.
(See the Target Tier Policy.)

Some changes occurred to the CTFE / Miri engine

cc @rust-lang/miri

[Noratrieb]

I will review this once CI passes. Looks like some functions got renamed but not everywhere.
@rustbot author

[jsoref]

This is_const_evaluatable stuff appears to be a mess that also involves crossing rust-clippy (I have an open PR for stuff in rust-clippy that shouldn't do any cross stuff) (in my original work, I was pretty sure that CI was happy with me, but splitting is hazardous and I'm imperfect). I'm going to drop it and if/when this merges, I can approach it separately.

[jsoref]

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.

[Noratrieb]

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).

[Noratrieb]

r=me after squashing

[bors]

☔ The latest upstream changes (presumably #110458) made this pull request unmergeable. Please resolve the merge conflicts.

[Noratrieb]

@bors r+

[bors]

📌 Commit e09d0d2 has been approved by Nilstrieb

It is now in the queue for this repository.