-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
Tracking issue for [T]::rchunks, rchunks_mut, rchunks_exact, rchunks_exact_mut #55177
Copy link
Copy link
Closed
Closed
Copy link
Labels
B-unstableBlocker: Implemented in the nightly compiler and unstable.Blocker: Implemented in the nightly compiler and unstable.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.
Metadata
Metadata
Assignees
Labels
B-unstableBlocker: Implemented in the nightly compiler and unstable.Blocker: Implemented in the nightly compiler and unstable.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.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Implemented in #54580.
These are similar to
chunks,chunks_mut,chunks_exact, andchunks_exact_mutrespectively, but they start from the end of the slice. They differ from calling.rev()on those other iterators (which is also possible) when the slice’s length is not a multiple of the chunk size: the remainder (either a smaller chunk or accessible through a separate method) is at the start of the slice instead of the end.CC #47115 which tracks
chunks_exactandchunks_exact_mut.