move MIR syntax into a dedicated file and ping some people whenever it changes

[RalfJung]

Adding or changing MIR operations/statements/whatever should be under significant scrutiny wrt their wider impact, specified semantics, and so on. So let's start by putting all that into a dedicated file and pinging some people whenever that file changes.

This PR only moves definitions around, and then fiddles with imports until it all works again.

[rust-highfive]

r? @wesleywiser

(rust-highfive has picked a reviewer for you, use r? to override)

[RalfJung]

Cc @lcnr @rust-lang/wg-mir-opt let me know if I should add more people (or teams) to the mention list here.

[oli-obk]

@bors r+ p=1

let's move this along before it bitrots

[bors]

📌 Commit ef34e57a74ec16d60ba9ccb958dfafaed57a1785 has been approved by oli-obk

[bors]

⌛ Testing commit ef34e57a74ec16d60ba9ccb958dfafaed57a1785 with merge f6b29fbf3c31d9c42872943e76037572f3cfb823...

[bors]

💔 Test failed - checks-actions

[RalfJung]

Argh, sorry for that...

[RalfJung]

@bors r=oli-obk

[bors]

📌 Commit a58d8f6 has been approved by oli-obk

[bors]

⌛ Testing commit a58d8f6 with merge 9789394f4f43d9bd711558bb04ecb084753e745c...

[bors]

💔 Test failed - checks-actions

[RalfJung]

Still some rustdoc stuff...?

[RalfJung]

./x.py doc compiler/rustc_builtin_macros does not reproduce the error here.

I think I know how to fix this, but how can I check...?

EDIT: ah, it's in rustc_middle.

[RalfJung]

@bors r=oli-obk

[bors]

📌 Commit 6c990f4 has been approved by oli-obk

[bors]

⌛ Testing commit 6c990f4 with merge a9eb9c5...

[bors]

☀️ Test successful - checks-actions
Approved by: oli-obk
Pushing a9eb9c5 to master...

[rust-timer]

Finished benchmarking commit (a9eb9c5): comparison url.

Instruction count

• Primary benchmarks: mixed results
• Secondary benchmarks: 😿 relevant regressions found

	mean1	max	count2
Regressions 😿 (primary)	0.5%	0.5%	1
Regressions 😿 (secondary)	1.6%	4.3%	20
Improvements 🎉 (primary)	-0.3%	-0.4%	5
Improvements 🎉 (secondary)	-0.3%	-0.3%	3
All 😿🎉 (primary)	-0.2%	0.5%	6

Max RSS (memory usage)

Results

• Primary benchmarks: no relevant changes found
• Secondary benchmarks: mixed results

	mean1	max	count2
Regressions 😿 (primary)	N/A	N/A	0
Regressions 😿 (secondary)	3.3%	4.4%	2
Improvements 🎉 (primary)	N/A	N/A	0
Improvements 🎉 (secondary)	-1.4%	-1.4%	1
All 😿🎉 (primary)	N/A	N/A	0

Cycles

Results

• Primary benchmarks: 😿 relevant regression found
• Secondary benchmarks: 😿 relevant regression found

	mean1	max	count2
Regressions 😿 (primary)	3.3%	3.3%	1
Regressions 😿 (secondary)	2.6%	2.6%	1
Improvements 🎉 (primary)	N/A	N/A	0
Improvements 🎉 (secondary)	N/A	N/A	0
All 😿🎉 (primary)	3.3%	3.3%	1

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression

Footnotes

1. the arithmetic mean of the percent change↩↩²↩³

2. number of relevant changes↩↩²↩³

[rust-timer]

Finished benchmarking commit (a9eb9c5): comparison url.

Instruction count

• Primary benchmarks: mixed results
• Secondary benchmarks: 😿 relevant regressions found

	mean1	max	count2
Regressions 😿 (primary)	0.5%	0.5%	1
Regressions 😿 (secondary)	1.6%	4.3%	20
Improvements 🎉 (primary)	-0.3%	-0.4%	5
Improvements 🎉 (secondary)	-0.3%	-0.3%	3
All 😿🎉 (primary)	-0.2%	0.5%	6

Max RSS (memory usage)

Results

• Primary benchmarks: no relevant changes found
• Secondary benchmarks: mixed results

	mean1	max	count2
Regressions 😿 (primary)	N/A	N/A	0
Regressions 😿 (secondary)	3.3%	4.4%	2
Improvements 🎉 (primary)	N/A	N/A	0
Improvements 🎉 (secondary)	-1.4%	-1.4%	1
All 😿🎉 (primary)	N/A	N/A	0

Cycles

Results

• Primary benchmarks: 😿 relevant regression found
• Secondary benchmarks: 😿 relevant regression found

	mean1	max	count2
Regressions 😿 (primary)	3.3%	3.3%	1
Regressions 😿 (secondary)	2.6%	2.6%	1
Improvements 🎉 (primary)	N/A	N/A	0
Improvements 🎉 (secondary)	N/A	N/A	0
All 😿🎉 (primary)	3.3%	3.3%	1

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression

Footnotes

1. the arithmetic mean of the percent change↩↩²↩³

2. number of relevant changes↩↩²↩³

[RalfJung]

Oh, we're getting the news twice this time?^^