-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust self-type check to require equality #85511
Conversation
@bors r+ |
📌 Commit a4bb0ba533c6fa6cb073e9eae5630adb0de87a62 has been approved by |
@bors rollup=never - might want to bisect to this if it causes regressions in the wild |
⌛ Testing commit a4bb0ba533c6fa6cb073e9eae5630adb0de87a62 with merge ca72f607d93aeb36c5c8eef02e7b1a4a17d60b8f... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
@Mark-Simulacrum needs a bless? |
a4bb0ba
to
4b4382d
Compare
@bors r=nikomatsakis |
📌 Commit 4b4382d has been approved by |
☀️ Test successful - checks-actions |
When we encounter
SomeType::<X>::foo
,self_ty
isSomeType<X>
and the method is defined in an impl onSomeType<A>
. Previously, we required simply thatself_ty <: impl_ty
, but this is too lax: we should require equality in order to use the method. This was found as part of unrelated work on never type stabilization, but also fixes one of the wf test cases.