Consider unfulfilled obligations in binop errors

[estebank]

When encountering a binop where the types would have been accepted, if
all the predicates had been fulfilled, include information about the
predicates and suggest appropriate #[derive]s if possible.

Fix #84515.

[rust-highfive]

r? @petrochenkov

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

[petrochenkov]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit a44c45ad10fb8966b70277036614fc7816f9cba0 with merge 5971dfc06e85c9854f851f945da5040e0b31ba48...

[bors]

☀️ Try build successful - checks-actions
Build commit: 5971dfc06e85c9854f851f945da5040e0b31ba48 (5971dfc06e85c9854f851f945da5040e0b31ba48)

[rust-timer]

Queued 5971dfc06e85c9854f851f945da5040e0b31ba48 with parent 50f9f78, future comparison URL.

[rust-timer]

Finished benchmarking commit (5971dfc06e85c9854f851f945da5040e0b31ba48): comparison url.

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

• Moderate regression in instruction counts (up to 0.6% on incr-full builds of inflate)

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 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-review -S-waiting-on-perf +perf-regression

[estebank]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

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

[bors]

⌛ Trying commit 4d55ff29e5b641a20091ca8888ab129c192e6574 with merge 0cf952227f02aa71d77879ef66bbb3d1a477c9c2...

[estebank]

@petrochenkov, sorry I hadn't realized we changed the waiting-on labels back and forth. Why should this be waiting on author? It addresses your review comments and ran a perf to verify that it has no impact (I don't see why it would).

[petrochenkov]

I set the label after writing #89323 (comment) and before the last commit appeared, now it's waiting on perf, I guess.

[rust-timer]

Queued dac9ca84fd7135880faa8885c21db395c7841a6e with parent c02371c, future comparison URL.

[rust-timer]

Finished benchmarking commit (dac9ca84fd7135880faa8885c21db395c7841a6e): comparison url.

Summary: This benchmark run did not return any relevant changes.

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.

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

[petrochenkov]

r=me with commits squashed.

[estebank]

@bors r=petrochenkov

[bors]

📌 Commit e8fc076 has been approved by petrochenkov

[bors]

⌛ Testing commit e8fc076 with merge d7539a6...

[bors]

☀️ Test successful - checks-actions
Approved by: petrochenkov
Pushing d7539a6 to master...

[rust-timer]

Finished benchmarking commit (d7539a6): comparison url.

Summary: This benchmark run did not return any relevant changes.

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

@rustbot label: -perf-regression