GCI: At their def site, actually wfcheck the where-clause & always eval free lifetime-generic constants

[fmease]

• 1st commit: Partially addresses #136204 by turning const eval errors from post to pre-mono for free lifetime-generic constants.
  • As the linked issue/comment states, on master there's a difference between const _: () = panic!(); (pre-mono error) and const _<'a>: () = panic!(); (post-mono error) which feels wrong.
  • With this PR, both become pre-mono ones!
• 2nd commit: Oof, yeah, I missed that in the initial impl!

This doesn't fully address #136204 because I still haven't figured out how & where to properly & best suppress const eval of free constants whose predicates don't hold at the def site. The motivating example is const _UNUSED: () = () where for<'_delay> String: Copy; which can also be found over at the tracking issue #113521.

r? compiler-errors or reassign

[fmease]

@bors try @rust-timer queue

[bors]

⌛ Trying commit 5a8ee9b with merge ea1cdda...

[bors]

☀️ Try build successful - checks-actions
Build commit: ea1cdda (ea1cdda3b51a1290675800f2196813f4bfc693bd)

[rust-timer]

Finished benchmarking commit (ea1cdda): comparison URL.

Overall result: ❌ regressions - please read the text below

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf.

Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

@bors rollup=never
@rustbot label: -S-waiting-on-perf +perf-regression

Instruction count

This is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.

	mean	range	count
Regressions ❌ (primary)	0.9%	[0.4%, 1.1%]	8
Regressions ❌ (secondary)	0.3%	[0.3%, 0.3%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.9%	[0.4%, 1.1%]	8

Max RSS (memory usage)

Results (primary 1.5%, secondary -2.0%)

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)	1.5%	[1.0%, 2.0%]	2
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.0%	[-2.0%, -2.0%]	1
All ❌✅ (primary)	1.5%	[1.0%, 2.0%]	2

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: 777.275s -> 776.801s (-0.06%)
Artifact size: 328.69 MiB -> 328.73 MiB (0.01%)

[rustbot]

Some changes occurred to the CTFE / Miri interpreter

cc @rust-lang/miri, @rust-lang/wg-const-eval

[fmease]

@bors try @rust-timer queue

[bors]

⌛ Trying commit 9f2fdff with merge 6f11489...

[bors]

☀️ Try build successful - checks-actions
Build commit: 6f11489 (6f11489377389dbe08c91408f1c8f953933c18cd)

[RalfJung]

turning const eval errors from post to pre-mono for free lifetime-generic constants.

This should be listed as an item in the tracking issue to make sure it is discussed during stabilization.

[fmease]

Oh no :( @bors r-

[fmease]

Right, in #140672 errs made us deeply normalize during WF in the next solver which didn't get picked up as a conflict during the rebase (good that a test caught it!). Fixed.

@bors r=BoxyUwU

[bors]

📌 Commit 9f12748 has been approved by BoxyUwU

It is now in the queue for this repository.