r? @compiler-errors

(rustbot has picked a reviewer for you, use r? to override)

Hey! It looks like you've submitted a new PR for the library teams!

If this PR contains changes to any rust-lang/rust public library APIs then please comment with @rustbot label +T-libs-api -T-libs to tag it appropriately. If this PR contains changes to any unstable APIs please edit the PR description to add a link to the relevant API Change Proposal or create one if you haven't already. If you're unsure where your change falls no worries, just leave it as is and the reviewer will take a look and make a decision to forward on if necessary.

Examples of T-libs-api changes:

• Stabilizing library features
• Introducing insta-stable changes such as new implementations of existing stable traits on existing stable types
• Introducing new or changing existing unstable library APIs (excluding permanently unstable features / features without a tracking issue)
• Changing public documentation in ways that create new stability guarantees
• Changing observable runtime behavior of library APIs

This PR changes MIR

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

Some changes occurred in src/tools/rust-analyzer

cc @rust-lang/rust-analyzer

please squash this into one commit, then i can approve

(Sorry for the ping spam MIR & RA peeps, just a bunch of comment changes 😅)

Also, actually, the guidance is typically to leave tools alone. Can you revert that rust-analyzer change?

Done & Squashed 👏🏻

@bors r+ rollup

📌 Commit e5a5b90 has been approved by compiler-errors

It is now in the queue for this repository.