[WIP] Use all projection sub-obligations during trait evaluation

[Aaron1011]

No description provided.

[rust-highfive]

r? @varkor

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

[Aaron1011]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit bf6052a3b1b74fdf9990f232d842baff862bd21a with merge 2bdc771d8c8b40c585b9a67069f4e8237a0a2316...

[bors]

☀️ Try build successful - checks-actions
Build commit: 2bdc771d8c8b40c585b9a67069f4e8237a0a2316 (2bdc771d8c8b40c585b9a67069f4e8237a0a2316)

[rust-timer]

Queued 2bdc771d8c8b40c585b9a67069f4e8237a0a2316 with parent 952fdf2, future comparison URL.

[rust-timer]

Finished benchmarking try commit (2bdc771d8c8b40c585b9a67069f4e8237a0a2316): comparison url.

Summary: This change led to significant regressions 😿 in compiler performance.

• Large regression in instruction counts (up to 8.0% on full builds of deeply-nested-check)

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

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 led to changes in compiler 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 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-review -S-waiting-on-perf +perf-regression

[bors]

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

[camelid]

triage: Should this be closed in favor of #85868?