Tracking Issue for VecDeque::extract_if
Open
Nobody has claimed this yet.
C-tracking-issue
S-tracking-unimplemented
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(vec_deque_extract_if)]
This is a tracking issue for https://github.com/rust-lang/libs-team/issues/673
Public API
Almost the same as vec::ExtractIf but for VecDeque:
impl<T, A: Allocator> VecDeque<T, A> {
pub fn extract_if<F, R>(&mut self, range: R, filter: F) -> ExtractIf<'_, T, F, A>
where
F: FnMut(&mut T) -> bool,
R: RangeBounds<usize>,
{
ExtractIf::new(self, filter, range)
}
}
pub struct ExtractIf<'a, T, F, A: Allocator = Global> {
vec: &'a mut VecDeque<T, A>,
idx: usize,
end: usize,
del: usize,
old_len: usize,
pred: F,
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: https://github.com/rust-lang/libs-team/issues/673
- Implementation: https://github.com/rust-lang/rust/pull/147780
- 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
Read the public API and the linked ACP and implementation PR first; the implementation step is already checked off. The remaining work is the final comment period and stabilization PR, so verify the feature lifecycle guidance and current issue status before attempting any contribution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100