-
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
[beta] back out #53793 - stabilize outlives requirements #54877
Conversation
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
|
@Mark-Simulacrum They are; but we could also drop it from 2018 if it can't be done. However, that would be quite unfortunate and make 2018 less exciting. As for finding the underlying cause I can't help out myself, but I do think it's worth prioritizing this. I'd wait for @aturon's input tho. |
Perhaps I am missing something. This PR merely removes the stabilization from the current beta — this change will still be considered stable on nightly and in RC2 when that branch breaks, and hence it will still be part of Rust 2018. It's just arriving a bit later to avoid a more complex backport. The only real reason I can see to land this change earlier would be to help us flush out more bugs, but finding those bugs on stable is usually not the sort of thing we try to do (rather, we tend to prefer to give a patch more time for testing on nightly and beta). |
r? @nikomatsakis -- stealing this from @eddyb |
@bors r+ |
📌 Commit e954510 has been approved by |
After some brief conversation on Discord, it seems clear we can move forward with this. |
@bors p=1 (beta backport) |
☀️ Test successful - status-appveyor, status-travis |
Fixes #54467 for beta, looks like a less risky fix than #54701