Normalize obligations for closure confirmation#88441
Conversation
There was a problem hiding this comment.
The duplication here is not nice, but I'd rather leave this for a followup PR.
| // ignore-compare-mode-nll | ||
| // fails in migrate, passes in nll |
There was a problem hiding this comment.
This is a bit weird, not sure
There was a problem hiding this comment.
I spent some time digging into this but I'm not sure what's going on yet.
|
☔ The latest upstream changes (presumably #88719) made this pull request unmergeable. Please resolve the merge conflicts. |
0900c2f to
c51f7e0
Compare
c51f7e0 to
cacc3ee
Compare
|
@bors r+ In our last discussion, @jackh726 and I figured out what was going wrong here, but we also decided it's a pre-existing bug that we should deal with separately. The problem is that, in the case of an impl with type parameters whose value is derived from an associated type binding like |
|
📌 Commit cacc3ee has been approved by |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (18cae26): 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 |
Based on #90017
Fixes #74261
Fixes #71955
Fixes #88459
r? @nikomatsakis