Rollup of 5 pull requests

[aliemjay]

Successful merges:

• Disable missing_copy_implementations lint on non_exhaustive types #116812 (Disable missing_copy_implementations lint on non_exhaustive types)
• Disable effects in libcore again #116856 (Disable effects in libcore again)
• Suggest constraining assoc types in more cases #116865 (Suggest constraining assoc types in more cases)
• Don't compare host param by name #116870 (Don't compare host param by name)
• revert #114586 #116879 (revert Bubble up opaque <eq> opaque operations instead of picking an order #114586)

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[aliemjay]

@bors r+ rollup=never p=5

[bors]

📌 Commit 8489bce has been approved by aliemjay

It is now in the queue for this repository.

[bors]

⌛ Testing commit 8489bce with merge e1de04a...

[bors]

☀️ Test successful - checks-actions
Approved by: aliemjay
Pushing e1de04a to master...

[rust-timer]

📌 Perf builds for each rolled up PR:

PR#	Message	Perf Build Sha
#116812	Disable missing_copy_implementations lint on non_exhaustive…	4d1720e03d8d2e0136309f2af7b6020f26686820 (link)
#116856	Disable effects in libcore again	309a65e090b50082a4b5df21f1f2ce62a07f1b61 (link)
#116865	Suggest constraining assoc types in more cases	f4f402ab8229afa1b5292762551b9c33c2918be4 (link)
#116870	Don't compare host param by name	9712dcaf7a473d9386838ea5195ff50d13d39b3c (link)
#116879	revert #114586	83c884d87b987f01c84c1a0ffbf330303a481318 (link)

previous master: e8b8c78d84

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

[rust-timer]

Finished benchmarking commit (e1de04a): comparison URL.

Overall result: ❌✅ regressions and improvements - ACTION NEEDED

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
cc @rust-lang/wg-compiler-performance

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	0.5%	[0.5%, 0.5%]	1
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-0.3%	[-0.5%, -0.2%]	9
Improvements ✅ (secondary)	-0.6%	[-0.9%, -0.3%]	13
All ❌✅ (primary)	-0.2%	[-0.5%, 0.5%]	10

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)	8.6%	[8.4%, 8.7%]	2
Regressions ❌ (secondary)	2.2%	[0.5%, 3.8%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.7%	[-4.1%, -0.7%]	3
All ❌✅ (primary)	8.6%	[8.4%, 8.7%]	2

Cycles

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

Binary size

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.2%	[0.0%, 0.5%]	5
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-0.1%	[-0.3%, -0.0%]	29
Improvements ✅ (secondary)	-0.1%	[-0.2%, -0.0%]	14
All ❌✅ (primary)	-0.0%	[-0.3%, 0.5%]	34

Bootstrap: 631.223s -> 629.235s (-0.31%)
Artifact size: 304.04 MiB -> 303.99 MiB (-0.02%)

[nnethercote]

Improvement outweigh regressions. I wonder which one was responsible. Maybe #116812?

@rustbot label: +perf-regression-triaged