-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Tracking Issue for slice::split_at in const context #101158
Comments
…t, r=Mark-Simulacrum add tracking issue number to const_slice_split_at_not_mut Add issue number rust-lang#101158 to `const_slice_split_at_not_mut` feature.
…t, r=Mark-Simulacrum add tracking issue number to const_slice_split_at_not_mut Add issue number rust-lang#101158 to `const_slice_split_at_not_mut` feature.
@rfcbot merge cc @rust-lang/wg-const-eval |
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. |
…t, r=dtolnay Stabilize const slice::split_at This stabilizes the use of the following method in const context: ```rust impl<T> [T] { pub const fn split_at(&self, mid: usize) -> (&[T], &[T]); } ``` cc tracking issue rust-lang#101158
Stabilization PR landed; closing. |
Feature gate:
#![feature(const_slice_split_at_not_mut)]
This is a tracking issue for usage of
slice::split_at
in const context.Public API
Steps / History
Unresolved Questions
The text was updated successfully, but these errors were encountered: