-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
variant of PR 87770 with limited scope for backport. #91136
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
|
e96fa7b
to
f9ee681
Compare
(The compiler team itself hasn't discussed whether we would be better off backporting this, or backporting PR #90840 itself. I believe we will resolve that question on Wednesday.) |
I'm probably not a good reviewer here -- r? @jackh726 perhaps? |
This implementation looks good to me, but I don't know if its strictly better than #90840 for backport. Does the new test you added also pass on master? We probably want that test added regardless. On one hand, this is somewhat of a revert to #87770, which is "safer". On the other, it's pretty clear that the cause of the issue was just a failure to relate the lifetimes. I'll leave the decision to backport this or #90840 to the compiler team, but I personally prefer the latter out of consistency. However, r=me on this implementation. |
(Closing; We'll backport #90840 instead of this.) |
This version does not attempt to resolve the problem that is illustrated by src/test/ui/const-generics/generic_const_exprs/drop_impl.rs (a problem that relies on nightly features to demonstrate anyway).
My thinking is that this is a better choice for backporting to stable and beta.
Fix #90838 (which was closed by accident by #90840, which only landed on nightly, so far).