-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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 deque_range #79022
stabilize deque_range #79022
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @m-ou-se (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
@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. |
☔ The latest upstream changes (presumably #79065) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
@SpyrosRoum Looks like you accidentally pulled in changes a few unrelated commits into this PR while addressing the merge conflict. Try rebasing: |
I think I didn't do the correct thing. Sorry I'm not that familiar with git and actually working with other people 😅 |
@Amanieu @KodrAus @sfackler @withoutboats this is waiting on your vote/concerns |
🔔 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. The RFC will be merged soon. |
@bors r+ rollup |
📌 Commit 161300d has been approved by |
This has |
☀️ Test successful - checks-actions |
Fix stabilization version of deque_range feature. See rust-lang#79022 (comment)
This needs |
Update RELEASES.md A couple of things that were missing in the release notes: - `Div` and `Rem` by their `NonZero` variant is now implemented for all unsigned integers (rust-lang#79134) - Stabilization of `VecDeque::range` and `VecDeque::range_mut` (rust-lang#79022, stabilization version corrected to 1.51.0 rust-lang#80448) - Deprecation of `spin_loop_hint` (rust-lang#80966)
Update RELEASES.md A couple of things that were missing in the release notes: - `Div` and `Rem` by their `NonZero` variant is now implemented for all unsigned integers (rust-lang#79134) - Stabilization of `VecDeque::range` and `VecDeque::range_mut` (rust-lang#79022, stabilization version corrected to 1.51.0 rust-lang#80448) - Deprecation of `spin_loop_hint` (rust-lang#80966)
Update RELEASES.md A couple of things that were missing in the release notes: - `Div` and `Rem` by their `NonZero` variant is now implemented for all unsigned integers (rust-lang#79134) - Stabilization of `VecDeque::range` and `VecDeque::range_mut` (rust-lang#79022, stabilization version corrected to 1.51.0 rust-lang#80448) - Deprecation of `spin_loop_hint` (rust-lang#80966)
Make #74217 stable, stabilizing
VecDeque::range
andVecDeque::range_mut
.Pr: #74099
r? @m-ou-se