-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Workaround for #28871 #29241
Workaround for #28871 #29241
Conversation
trait definitions, and give prefence to the former. This is consistent with what we do for selection. It also works around a limitation that was leading to rust-lang#28871.
@rust-lang/lang nominating this for backport to beta. I'd like to do so tomorrow. |
Presuming we opt to land it, I'm ok w/ backporting this; it's a very minor patch, fixes a regression. (That was, indeed, the point.) |
I would prefer to normalize the projection's trait-ref (so they will deduplicate), but I guess this makes sense too. |
r+ modulo the test working. |
In general I prefer that as well. I didn't have much time yesterday so I On Fri, Oct 23, 2015 at 9:20 AM, arielb1 notifications@github.com wrote:
|
@bors r+ |
📌 Commit b69e08c has been approved by |
Given the time frame, I'm going to declare this beta-accepted, as I don't anticipate any objections from @rust-lang/lang members. Let me know if I am mistaken. |
Give preference to projections from where-clauses over those from trait definitions. This makes #28871 work again, though I think there's more to fix in this general area.
r? @arielb1
cc @brson (fixes regression)