rename Generator to Coroutine

[oli-obk]

implements rust-lang/compiler-team#682

While I did an automated replacement, I went through all changes manually to avoid renaming things like "id generators", "code generator", ...

I renamed files where that was necessary due to the contents referring to the crate name itself (mir opt, codegen or debuginfo tests), or required by tidy (feature gate docs)

• rename various remaining abbreviated references to generators.
• rename files
• rename folders
• add renamed feature: generators, ...

r? @ghost

[rustbot]

This PR changes MIR

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

Some changes occurred in src/tools/clippy

cc @rust-lang/clippy

This PR changes Stable MIR

cc @oli-obk, @celinval, @spastorino

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 compiler/rustc_codegen_cranelift

cc @bjorn3

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 in compiler/rustc_codegen_gcc

cc @antoyo

Some changes occurred in src/tools/rustfmt

cc @rust-lang/rustfmt

This PR changes Stable MIR

cc @oli-obk, @celinval, @spastorino, @ouz-a

The Miri subtree was changed

cc @rust-lang/miri

[bors]

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

[pnkfelix]

I skimmed this. It looks good, though a line-by-line review is not feasible nor a reasonable use of effort.

(At some point one is best off trusting that the compiler is going to catch any omissions when it comes to a rewrite like this, since it seems very unlikely that an overlooked rename is going to pass the compiler unless all relevant instances in that scope were equally overlooked, which means no observable change in behavior.)

I'm assigning high priority to this because it's going to bitrot nearly immediately.

@bors r+ rollup=never p=3

[bors]

📌 Commit bdd049d has been approved by pnkfelix

It is now in the queue for this repository.

[oli-obk]

@bors r- CI failed again 😆

[oli-obk]

@bors r=pnkfelix

[rust-timer]

Finished benchmarking commit (249624b): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	2.2%	[1.1%, 3.3%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-3.3%	[-3.9%, -2.8%]	2
All ❌✅ (primary)	-	-	0

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 631.391s -> 631.871s (0.08%)
Artifact size: 304.06 MiB -> 304.05 MiB (-0.00%)

[pthariensflame]

@oli-obk Missed a spot: core/ops/coroutine.rs

Coroutines, also commonly referred to as coroutines

There are also a couple of “coroutines/coroutines” in the Unstable Book.