Tracking Issue for `BinaryHeap::extract_if`
Open
Nobody has claimed this yet.
C-tracking-issue
S-tracking-unimplemented
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(binary_heap_extract_if)]
This is a tracking issue for BinaryHeap::extract_if from rust-lang/rfcs#2140
Public API
// alloc::binary_heap;
pub struct BinaryHeap<T, A>;
impl<T, A: Allocator> BinaryHeap<T, A> {
pub fn extract_if<F>(&mut self, pred: F) -> ExtractIf<'_, T, F, A>;
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: rust-lang/libs-team#...
- Implementation: #42849
- 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 RFC rust-lang/rfcs#2140 and the public API shown for BinaryHeap::extract_if, then review the implementation tracked as #42849. The issue is complete when the ACP, implementation, final comment period, and stabilization PR checklist steps are resolved.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100