Rollup of 4 pull requests

[Zalathar]

Successful merges:

• const select_unpredictable #145939 (const select_unpredictable)
• More intuitive error when using self to instantiate tuple struct with private field #147478 (More intuitive error when using self to instantiate tuple struct with private field)
• Add built-in const impls for Clone and Copy #147866 (Add built-in const impls for Clone and Copy)
• Fix duplicate 'the the' typos in comments #148153 (Fix duplicate 'the the' typos in comments)

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[Zalathar]

Rollup of everything.

@bors r+ rollup=never p=5

[bors]

📌 Commit 791165c has been approved by Zalathar

It is now in the queue for this repository.

[bors]

⌛ Testing commit 791165c with merge 9ea8d67...

[bors]

☀️ Test successful - checks-actions
Approved by: Zalathar
Pushing 9ea8d67 to master...

[rust-timer]

📌 Perf builds for each rolled up PR:

PR#	Message	Perf Build Sha
#145939	const select_unpredictable	1940cfd70ac51a1f0b54ce09835ebd6ec2f97896 (link)
#147478	More intuitive error when using self to instantiate tuple s…	dd31609a61c0a3b604d92eb7994082a73c4d438e (link)
#147866	Add built-in const impls for Clone and Copy	ffdb097404b100b80d8fc8ead681e44ee8058ef6 (link)
#148153	Fix duplicate 'the the' typos in comments	fc133bf9ffed99526e9a8b37f09683edc2b48c92 (link)

previous master: 4b53279854

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

[github-actions]

What is this?

This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 4b53279 (parent) -> 9ea8d67 (this PR)

Test differences

Show 165 test diffs

Stage 1

• [ui] tests/ui/resolve/private-constructor-self-issue-147343.rs: [missing] -> pass (J1)

Stage 2

• [ui] tests/ui/resolve/private-constructor-self-issue-147343.rs: [missing] -> pass (J0)

Additionally, 163 doctest diffs were found. These are ignored, as they are noisy.

Job group index

• J0: aarch64-apple, aarch64-gnu, aarch64-gnu-llvm-20-1, aarch64-msvc-1, arm-android, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, i686-msvc-1, test-various, x86_64-gnu, x86_64-gnu-debug, x86_64-gnu-gcc, x86_64-gnu-llvm-20, x86_64-gnu-llvm-20-2, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1
• J1: x86_64-gnu-llvm-20-3

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 9ea8d67cc60e88ad6fffbf299a454c44227e001c --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

1. pr-check-1: 1438.6s -> 1852.4s (28.8%)
2. aarch64-gnu-llvm-20-1: 3288.0s -> 3683.3s (12.0%)
3. dist-various-1: 4179.7s -> 3730.3s (-10.8%)
4. test-various: 6279.4s -> 6938.5s (10.5%)
5. dist-aarch64-msvc: 5341.7s -> 5866.1s (9.8%)
6. aarch64-apple: 10864.5s -> 9808.2s (-9.7%)
7. x86_64-rust-for-linux: 2795.3s -> 2532.5s (-9.4%)
8. i686-gnu-nopt-1: 7863.3s -> 8544.3s (8.7%)
9. dist-apple-various: 3793.1s -> 4102.4s (8.2%)
10. aarch64-msvc-2: 5241.4s -> 4816.2s (-8.1%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

[rust-timer]

Finished benchmarking commit (9ea8d67): 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 (secondary -3.2%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-3.2%	[-3.9%, -2.5%]	2
All ❌✅ (primary)	-	-	0

Cycles

Results (primary 2.5%, secondary 8.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	2.5%	[2.1%, 2.7%]	3
Regressions ❌ (secondary)	8.0%	[6.3%, 9.6%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	2.5%	[2.1%, 2.7%]	3

Binary size

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

Bootstrap: 474.938s -> 474.628s (-0.07%)
Artifact size: 390.59 MiB -> 390.61 MiB (0.01%)