-
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
Stabilized vec_splice and modified splice tracking issue #44640
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @BurntSushi (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. |
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.
Sorry it isn't clear from the tracking issue -- but when the libs team discussed stabilizing Vec::splice and String::splice, we decided to stabilize Vec::splice but try a new signature for String::splice and keep it unstable. I left a comment on the tracking issue just now to clarify this.
Please keep the unstable attribute on String::splice for now and change its tracking issue number to point to #44643. Since we are stabilizing one but not the other, they will need to have different feature names. We can minimize breakage by changing Vec::splice to be under the now-stable feature vec_splice and keeping String::splice under feature(splice).
#[stable(feature = "vec_splice", since = "1.22.0")]
#[unstable(feature = "splice", reason = "...", issue = "44643")]
Thanks!
Thanks for the heads-up! I'll do it later today. |
74d5069
to
6b167f9
Compare
@dtolnay Done! |
@bors r+ rollup |
📌 Commit 6b167f9 has been approved by |
Stabilized vec_splice and modified splice tracking issue This stabilizes the vec_splice (Vec part of splice RFC) Fixes rust-lang#32310.
Stabilized vec_splice and modified splice tracking issue This stabilizes the vec_splice (Vec part of splice RFC) Fixes rust-lang#32310.
This includes the following stabilizations: - tcpstream_connect_timeout rust-lang#44563 - iterator_for_each rust-lang#44567 - ord_max_min rust-lang#44593 - compiler_fences rust-lang#44595 - needs_drop rust-lang#44639 - vec_splice rust-lang#44640
This includes the following stabilizations: - tcpstream_connect_timeout rust-lang#44563 - iterator_for_each rust-lang#44567 - ord_max_min rust-lang#44593 - compiler_fences rust-lang#44595 - needs_drop rust-lang#44639 - vec_splice rust-lang#44640
[beta] Backport accepted PRs to 1.21 Backport of: - ~don't suggest placing `use` statements into expanded code #44215 - stabilize tcpstream_connect_timeout #44563 - stabilized iterator_for_each #44567 - travis: Move sccache to the us-west-1 region #44574 - stabilized ord_max_min #44593 - stabilized compiler_fences #44595 - ci: Upload/download from a new S3 bucket #44617 - stabilized needs_drop #44639 - Stabilized vec_splice and modified splice tracking issue #44640 - Backport libs stabilizations to 1.21 beta #44824
Backport libs stabilizations to 1.21 beta Includes the following stabilizations: - tcpstream_connect_timeout rust-lang#44563 - iterator_for_each rust-lang#44567 - ord_max_min rust-lang#44593 - compiler_fences rust-lang#44595 - needs_drop rust-lang#44639 - vec_splice rust-lang#44640 These have been backported in rust-lang#44823.
This stabilizes the vec_splice (Vec part of splice RFC)
Fixes #32310.