-
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
Stabilize const-weak-new #95965
Stabilize const-weak-new #95965
Conversation
Thank you for submitting a new PR for the library teams! If this PR contains a stabilization of a library feature that has not already completed FCP in its tracking issue, introduces new or changes existing unstable library APIs, or changes our public documentation in ways that create new stability guarantees then please comment with |
r? @m-ou-se (rust-highfive has picked a reviewer for you, use r? to override) |
r? rust-lang/libs-api @rustbot label +T-libs-api |
(triaging my open PRs) It's been a bit; attempting reviewer rotation. (I also need to bump the stabilized version; will do later.) r? rust-lang/libs-api Requesting I-libs-api-nominated T-libs-api nomination for FCP. |
@rfcbot merge |
Team member @m-ou-se has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. |
👋 Hello, I'm writing this comment in this stabilization PR to notify you, the authors of this PR, that #100591 has been merged, which implemented a change in how features are stabilized. Your PR has been filed before the change, so will likely require modifications in order to comply with the new rules. I recommend you to:
That's it! The If you have any questions, feel free to drop by the zulip stream, or ping me directly in this PR's thread. Thanks! 👋 |
Just wondering, what's the situation with this PR? It seems ready to be merged (except for that last comment), but nothing has happened for a couple months now. |
In theory it should get merged if I rebase it for the new process. (I had lost track of and forgotten that it was waiting on me for such.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needed change for the new release process
@CAD97 I think my suggestion is the only change needed. Are you able to apply those and rebase soon? If not, I can do so and open a separate PR - but it's nicer to keep this together if you can. |
It looks like @Dylan-DPC was able to apply my suggestions from above, so I believe this is ready for rereview/merge. @m-ou-se are you able to update the labels and/or merge? |
I believe this still needs a squash but it's ready for review regardless. |
Bump its stabilization version several times along the way to accommodate changes in release processes. Co-authored-by: Mara Bos <[email protected]> Co-authored-by: Trevor Gross <[email protected]>
8f2a068
to
ee29d2f
Compare
crunch |
@bors r+ rollup |
Stabilize const-weak-new This is a fairly uncontroversial library stabilization, so I'm going ahead and proposing it to ride the trains to stable. This stabilizes the following APIs, which are defined to be non-allocating constructors. ```rust // alloc::rc impl<T> Weak<T> { pub const fn new() -> Weak<T>; } // alloc::sync impl<T> Weak<T> { pub const fn new() -> Weak<T>; } ``` Closes rust-lang#95091 `@rustbot` modify labels: +needs-fcp
…kingjubilee Rollup of 4 pull requests Successful merges: - rust-lang#95965 (Stabilize const-weak-new) - rust-lang#109075 (Use `LazyLock` to lazily resolve backtraces) - rust-lang#113741 (Don't install default projection bound for return-position `impl Trait` in trait methods with no body) - rust-lang#114268 (Fix empty_write since rust version attribute) r? `@ghost` `@rustbot` modify labels: rollup
This is a fairly uncontroversial library stabilization, so I'm going ahead and proposing it to ride the trains to stable.
This stabilizes the following APIs, which are defined to be non-allocating constructors.
Closes #95091
@rustbot modify labels: +needs-fcp