Tracking Issue for `Iterator::exactly_one` and `Iterator::collect_array`
Open
Nobody has claimed this yet.
C-tracking-issue
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(exact_length_collection)]
This is a tracking issue for exact length collection, concerning originally one but after discussion two new APIs on iterators:
exactly_one()to collect the one and only element from an iteratorcollect_array()to collect an iterator into an array of an exact predetermined length.
Public API
// trait Iterator
// note: unlike itertools, returns an Option, not a result as per ACP
fn exactly_one(self) -> Option<Self::Item>
where
Self: Sized;
fn collect_array<const N: usize>(self) -> Option<[Self::Item; N]>
where
Self: Sized;
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: rust-lang/libs-team#676
- Implementation: https://github.com/rust-lang/rust/pull/149270
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the public API shown in the issue and read the linked implementation PR (rust-lang/rust#149270) to understand the current state of both iterator methods. Done means completing the remaining Final Comment Period and stabilization PR steps, with the feature gate and tracking checklist updated accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100