Tracking Issue for `BinaryHeap::pop_if()`
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(binary_heap_pop_if)]
This is a tracking issue for https://github.com/rust-lang/libs-team/issues/731
Adds a pop_if() function to BinaryHeap mirroring Vec::pop_if()
Public API
// alloc::collections::binary_heap
impl<T, A> BinaryHeap<T, A> {
pub fn pop_if(&mut self, predicate: impl FnOnce(&T) -> bool) -> Option<T> { .. }
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: https://github.com/rust-lang/libs-team/issues/731
- Implementation: https://github.com/rust-lang/rust/pull/151829
- 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 alloc::collections::binary_heap API shown in the issue, then read the linked ACP and implementation PR. The implementation is already complete; remaining work is to follow the FCP and stabilization steps, with the feature considered done when those tracking items 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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100