-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Stabilize static lifetime in statics #39265
Conversation
All reactions
-
🎉 3 reactions
@est31 nice |
All reactions
Sorry, something went wrong.
☔ The latest upstream changes (presumably #39282) made this pull request unmergeable. Please resolve the merge conflicts. |
All reactions
Sorry, something went wrong.
Rebased. |
All reactions
Sorry, something went wrong.
☔ The latest upstream changes (presumably #39305) made this pull request unmergeable. Please resolve the merge conflicts. |
All reactions
Sorry, something went wrong.
8ac8f0d
to
35191d0
Compare
Rebased on top of @eddyb 's PR. Its really great to see how the PR made this change much easier, so it must have been a good refactor! |
All reactions
Sorry, something went wrong.
ping @nrc, would be a neat feature for 1.17! |
All reactions
Sorry, something went wrong.
@alexcrichton its currently blocked by #37928 |
All reactions
Sorry, something went wrong.
☔ The latest upstream changes (presumably #39563) made this pull request unmergeable. Please resolve the merge conflicts. |
All reactions
Sorry, something went wrong.
Now that beta branched, I would like to ask for beta backport nomination, so that already 1.16 would have it stabilized. |
All reactions
Sorry, something went wrong.
Backporting stabilizations is incredibly rare; I would prefer we didn't.
…On Sun, Feb 5, 2017 at 12:17 PM, est31 ***@***.***> wrote:
Now that beta branched, I would like to ask for beta backport nomination,
so that already 1.16 would have it stabilized.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#39265 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AABsinz7uaODUek9-kH2vDy48sM0xfYfks5rZgQlgaJpZM4LrsNh>
.
|
All reactions
Sorry, something went wrong.
@bors: r+ I would also recommend against backporting - I don't think we should reduce stabilisation time in general. |
All reactions
Sorry, something went wrong.
📌 Commit 0361dcf has been approved by |
All reactions
Sorry, something went wrong.
⌛ Testing commit 0361dcf with merge 443866e... |
All reactions
Sorry, something went wrong.
💔 Test failed - status-travis |
All reactions
Sorry, something went wrong.
@bors: r=nrc |
All reactions
Sorry, something went wrong.
📌 Commit 1c8cb8a has been approved by |
All reactions
Sorry, something went wrong.
#37928 is not yet closed, how is this being merged? |
All reactions
Sorry, something went wrong.
@bors: r- |
All reactions
Sorry, something went wrong.
85accdc
to
f8b6108
Compare
The documentation PR got merged, this is ready to be r+ed! |
All reactions
Sorry, something went wrong.
📌 Commit f8b6108 has been approved by |
All reactions
Sorry, something went wrong.
Sorry, something went wrong.
Stabilize static lifetime in statics Stabilize the "static_in_const" feature. Blockers before this PR can be merged: * [x] The [FCP with inclination to stabilize](#35897 (comment)) needs to be over. FCP lasts roughly three weeks, so will be over at Jan 25, aka this thursday. * [x] Documentation needs to be added (#37928) Closes #35897.
☀️ Test successful - status-appveyor, status-travis |
All reactions
Sorry, something went wrong.
Removing beta nomination as sentiment seems to be to not backport (also see #35897) |
All reactions
Sorry, something went wrong.
Successfully merging this pull request may close these issues.
None yet
Stabilize the "static_in_const" feature. Blockers before this PR can be merged:
Closes #35897.