- 
                Notifications
    
You must be signed in to change notification settings  - Fork 13.9k
 
Open
Labels
A-arrayArea: `[T; N]`Area: `[T; N]`C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Description
Feature gate: #![feature(array_into_iter_constructors)]
This is a tracking issue for the from_raw_partsnew_unchecked and empty constructors on core::array::IntoIter.
This allows creating such an iterator with something other than a fully-initialized array.
Public API
// core::array
impl<T, const N: usize> IntoIter<T, N> {
    pub const fn empty() -> Self;
    pub const unsafe fn new_unchecked(buffer: [MaybeUninit<T>; N], initialized: Range<usize>) -> Self;
}Steps / History
-  Implementation: Add 
array::IntoIter::{empty, from_raw_parts}#91341 - Final comment period (FCP)
 - Stabilization PR
 
Unresolved Questions
-  Should this be named 
from_raw_partsor something else? -  Should this have to go through an 
ArrayVec-like type (like howVechasfrom_raw_partsinstead ofvec::IntoIterhaving it), instead of making theIntoIterdirectly? -  What's a good name for 
new_unchecked? It was previouslyfrom_raw_parts, but was changed at reviewer request in the initial PR. Then after that,newwas deprecated, which makes me feel likenew_uncheckedis a bit odd too.- Add 
Iterator::next_chunk#93700 (temporarily) added a duplicate of this calledwith_partial, so that's another possible name. 
 - Add 
 
ChayimFriedman2, clarfonthey, AjaxGb, Philippe-Cholet, ogau and 2 more
Metadata
Metadata
Assignees
Labels
A-arrayArea: `[T; N]`Area: `[T; N]`C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.