# Struct alloc::collections::binary_heap::BinaryHeap

1.0.0 · source · `pub struct BinaryHeap<T> { /* private fields */ }`

## Expand description

A priority queue implemented with a binary heap.

This will be a max-heap.

It is a logic error for an item to be modified in such a way that the
item’s ordering relative to any other item, as determined by the `Ord`

trait, changes while it is in the heap. This is normally only possible
through interior mutability, global state, I/O, or unsafe code. The
behavior resulting from such a logic error is not specified, but will
be encapsulated to the `BinaryHeap`

that observed the logic error and not
result in undefined behavior. This could include panics, incorrect results,
aborts, memory leaks, and non-termination.

As long as no elements change their relative order while being in the heap
as described above, the API of `BinaryHeap`

guarantees that the heap
invariant remains intact i.e. its methods all behave as documented. For
example if a method is documented as iterating in sorted order, that’s
guaranteed to work as long as elements in the heap have not changed order,
even in the presence of closures getting unwinded out of, iterators getting
leaked, and similar foolishness.

## Examples

```
use std::collections::BinaryHeap;
// Type inference lets us omit an explicit type signature (which
// would be `BinaryHeap<i32>` in this example).
let mut heap = BinaryHeap::new();
// We can use peek to look at the next item in the heap. In this case,
// there's no items in there yet so we get None.
assert_eq!(heap.peek(), None);
// Let's add some scores...
heap.push(1);
heap.push(5);
heap.push(2);
// Now peek shows the most important item in the heap.
assert_eq!(heap.peek(), Some(&5));
// We can check the length of a heap.
assert_eq!(heap.len(), 3);
// We can iterate over the items in the heap, although they are returned in
// a random order.
for x in &heap {
println!("{x}");
}
// If we instead pop these scores, they should come back in order.
assert_eq!(heap.pop(), Some(5));
assert_eq!(heap.pop(), Some(2));
assert_eq!(heap.pop(), Some(1));
assert_eq!(heap.pop(), None);
// We can clear the heap of any remaining items.
heap.clear();
// The heap should now be empty.
assert!(heap.is_empty())
```

RunA `BinaryHeap`

with a known list of items can be initialized from an array:

```
use std::collections::BinaryHeap;
let heap = BinaryHeap::from([1, 5, 2]);
```

Run### Min-heap

Either `core::cmp::Reverse`

or a custom `Ord`

implementation can be used to
make `BinaryHeap`

a min-heap. This makes `heap.pop()`

return the smallest
value instead of the greatest one.

```
use std::collections::BinaryHeap;
use std::cmp::Reverse;
let mut heap = BinaryHeap::new();
// Wrap values in `Reverse`
heap.push(Reverse(1));
heap.push(Reverse(5));
heap.push(Reverse(2));
// If we pop these scores now, they should come back in the reverse order.
assert_eq!(heap.pop(), Some(Reverse(1)));
assert_eq!(heap.pop(), Some(Reverse(2)));
assert_eq!(heap.pop(), Some(Reverse(5)));
assert_eq!(heap.pop(), None);
```

Run## Time complexity

The value for `push`

is an expected cost; the method documentation gives a
more detailed analysis.

## Implementations§

source§### impl<T: Ord> BinaryHeap<T>

### impl<T: Ord> BinaryHeap<T>

source#### pub fn new() -> BinaryHeap<T>

#### pub fn new() -> BinaryHeap<T>

source#### pub fn with_capacity(capacity: usize) -> BinaryHeap<T>

#### pub fn with_capacity(capacity: usize) -> BinaryHeap<T>

Creates an empty `BinaryHeap`

with at least the specified capacity.

The binary heap will be able to hold at least `capacity`

elements without
reallocating. This method is allowed to allocate for more elements than
`capacity`

. If `capacity`

is 0, the binary heap will not allocate.

##### Examples

Basic usage:

```
use std::collections::BinaryHeap;
let mut heap = BinaryHeap::with_capacity(10);
heap.push(4);
```

Run1.12.0 · source#### pub fn peek_mut(&mut self) -> Option<PeekMut<'_, T>>

#### pub fn peek_mut(&mut self) -> Option<PeekMut<'_, T>>

Returns a mutable reference to the greatest item in the binary heap, or
`None`

if it is empty.

Note: If the `PeekMut`

value is leaked, some heap elements might get
leaked along with it, but the remaining elements will remain a valid
heap.

##### Examples

Basic usage:

```
use std::collections::BinaryHeap;
let mut heap = BinaryHeap::new();
assert!(heap.peek_mut().is_none());
heap.push(1);
heap.push(5);
heap.push(2);
{
let mut val = heap.peek_mut().unwrap();
*val = 0;
}
assert_eq!(heap.peek(), Some(&2));
```

Run##### Time complexity

If the item is modified then the worst case time complexity is *O*(log(*n*)),
otherwise it’s *O*(1).

source#### pub fn pop(&mut self) -> Option<T>

#### pub fn pop(&mut self) -> Option<T>

Removes the greatest item from the binary heap and returns it, or `None`

if it
is empty.

##### Examples

Basic usage:

```
use std::collections::BinaryHeap;
let mut heap = BinaryHeap::from([1, 3]);
assert_eq!(heap.pop(), Some(3));
assert_eq!(heap.pop(), Some(1));
assert_eq!(heap.pop(), None);
```

Run##### Time complexity

The worst case cost of `pop`

on a heap containing *n* elements is *O*(log(*n*)).

source#### pub fn push(&mut self, item: T)

#### pub fn push(&mut self, item: T)

Pushes an item onto the binary heap.

##### Examples

Basic usage:

```
use std::collections::BinaryHeap;
let mut heap = BinaryHeap::new();
heap.push(3);
heap.push(5);
heap.push(1);
assert_eq!(heap.len(), 3);
assert_eq!(heap.peek(), Some(&5));
```

Run##### Time complexity

The expected cost of `push`

, averaged over every possible ordering of
the elements being pushed, and over a sufficiently large number of
pushes, is *O*(1). This is the most meaningful cost metric when pushing
elements that are *not* already in any sorted pattern.

The time complexity degrades if elements are pushed in predominantly
ascending order. In the worst case, elements are pushed in ascending
sorted order and the amortized cost per push is *O*(log(*n*)) against a heap
containing *n* elements.

The worst case cost of a *single* call to `push`

is *O*(*n*). The worst case
occurs when capacity is exhausted and needs a resize. The resize cost
has been amortized in the previous figures.

1.5.0 · source#### pub fn into_sorted_vec(self) -> Vec<T>

#### pub fn into_sorted_vec(self) -> Vec<T>

1.11.0 · source#### pub fn append(&mut self, other: &mut Self)

#### pub fn append(&mut self, other: &mut Self)

Moves all the elements of `other`

into `self`

, leaving `other`

empty.

##### Examples

Basic usage:

```
use std::collections::BinaryHeap;
let mut a = BinaryHeap::from([-10, 1, 2, 3, 3]);
let mut b = BinaryHeap::from([-20, 5, 43]);
a.append(&mut b);
assert_eq!(a.into_sorted_vec(), [-20, -10, 1, 2, 3, 3, 5, 43]);
assert!(b.is_empty());
```

Runsource#### pub fn drain_sorted(&mut self) -> DrainSorted<'_, T> ⓘ

🔬This is a nightly-only experimental API. (`binary_heap_drain_sorted`

#59278)

#### pub fn drain_sorted(&mut self) -> DrainSorted<'_, T> ⓘ

`binary_heap_drain_sorted`

#59278)Clears the binary heap, returning an iterator over the removed elements in heap order. If the iterator is dropped before being fully consumed, it drops the remaining elements in heap order.

The returned iterator keeps a mutable borrow on the heap to optimize its implementation.

Note:

`.drain_sorted()`

is*O*(*n** log(*n*)); much slower than`.drain()`

. You should use the latter for most cases.

##### Examples

Basic usage:

```
#![feature(binary_heap_drain_sorted)]
use std::collections::BinaryHeap;
let mut heap = BinaryHeap::from([1, 2, 3, 4, 5]);
assert_eq!(heap.len(), 5);
drop(heap.drain_sorted()); // removes all elements in heap order
assert_eq!(heap.len(), 0);
```

Run1.70.0 · source#### pub fn retain<F>(&mut self, f: F)where
F: FnMut(&T) -> bool,

#### pub fn retain<F>(&mut self, f: F)where F: FnMut(&T) -> bool,

Retains only the elements specified by the predicate.

In other words, remove all elements `e`

for which `f(&e)`

returns
`false`

. The elements are visited in unsorted (and unspecified) order.

##### Examples

Basic usage:

```
use std::collections::BinaryHeap;
let mut heap = BinaryHeap::from([-10, -5, 1, 2, 4, 13]);
heap.retain(|x| x % 2 == 0); // only keep even numbers
assert_eq!(heap.into_sorted_vec(), [-10, 2, 4])
```

Runsource§### impl<T> BinaryHeap<T>

### impl<T> BinaryHeap<T>

source#### pub fn into_iter_sorted(self) -> IntoIterSorted<T> ⓘ

🔬This is a nightly-only experimental API. (`binary_heap_into_iter_sorted`

#59278)

#### pub fn into_iter_sorted(self) -> IntoIterSorted<T> ⓘ

`binary_heap_into_iter_sorted`

#59278)Returns an iterator which retrieves elements in heap order. This method consumes the original heap.

##### Examples

Basic usage:

```
#![feature(binary_heap_into_iter_sorted)]
use std::collections::BinaryHeap;
let heap = BinaryHeap::from([1, 2, 3, 4, 5]);
assert_eq!(heap.into_iter_sorted().take(2).collect::<Vec<_>>(), [5, 4]);
```

Runsource#### pub fn peek(&self) -> Option<&T>

#### pub fn peek(&self) -> Option<&T>

Returns the greatest item in the binary heap, or `None`

if it is empty.

##### Examples

Basic usage:

```
use std::collections::BinaryHeap;
let mut heap = BinaryHeap::new();
assert_eq!(heap.peek(), None);
heap.push(1);
heap.push(5);
heap.push(2);
assert_eq!(heap.peek(), Some(&5));
```

Run##### Time complexity

Cost is *O*(1) in the worst case.

source#### pub fn reserve_exact(&mut self, additional: usize)

#### pub fn reserve_exact(&mut self, additional: usize)

Reserves the minimum capacity for at least `additional`

elements more than
the current length. Unlike `reserve`

, this will not
deliberately over-allocate to speculatively avoid frequent allocations.
After calling `reserve_exact`

, capacity will be greater than or equal to
`self.len() + additional`

. Does nothing if the capacity is already
sufficient.

##### Panics

Panics if the new capacity overflows `usize`

.

##### Examples

Basic usage:

```
use std::collections::BinaryHeap;
let mut heap = BinaryHeap::new();
heap.reserve_exact(100);
assert!(heap.capacity() >= 100);
heap.push(4);
```

Runsource#### pub fn reserve(&mut self, additional: usize)

#### pub fn reserve(&mut self, additional: usize)

Reserves capacity for at least `additional`

elements more than the
current length. The allocator may reserve more space to speculatively
avoid frequent allocations. After calling `reserve`

,
capacity will be greater than or equal to `self.len() + additional`

.
Does nothing if capacity is already sufficient.

##### Panics

Panics if the new capacity overflows `usize`

.

##### Examples

Basic usage:

```
use std::collections::BinaryHeap;
let mut heap = BinaryHeap::new();
heap.reserve(100);
assert!(heap.capacity() >= 100);
heap.push(4);
```

Run1.63.0 · source#### pub fn try_reserve_exact(
&mut self,
additional: usize
) -> Result<(), TryReserveError>

#### pub fn try_reserve_exact( &mut self, additional: usize ) -> Result<(), TryReserveError>

Tries to reserve the minimum capacity for at least `additional`

elements
more than the current length. Unlike `try_reserve`

, this will not
deliberately over-allocate to speculatively avoid frequent allocations.
After calling `try_reserve_exact`

, capacity will be greater than or
equal to `self.len() + additional`

if it returns `Ok(())`

.
Does nothing if the capacity is already sufficient.

Note that the allocator may give the collection more space than it
requests. Therefore, capacity can not be relied upon to be precisely
minimal. Prefer `try_reserve`

if future insertions are expected.

##### Errors

If the capacity overflows, or the allocator reports a failure, then an error is returned.

##### Examples

```
use std::collections::BinaryHeap;
use std::collections::TryReserveError;
fn find_max_slow(data: &[u32]) -> Result<Option<u32>, TryReserveError> {
let mut heap = BinaryHeap::new();
// Pre-reserve the memory, exiting if we can't
heap.try_reserve_exact(data.len())?;
// Now we know this can't OOM in the middle of our complex work
heap.extend(data.iter());
Ok(heap.pop())
}
```

Run1.63.0 · source#### pub fn try_reserve(&mut self, additional: usize) -> Result<(), TryReserveError>

#### pub fn try_reserve(&mut self, additional: usize) -> Result<(), TryReserveError>

Tries to reserve capacity for at least `additional`

elements more than the
current length. The allocator may reserve more space to speculatively
avoid frequent allocations. After calling `try_reserve`

, capacity will be
greater than or equal to `self.len() + additional`

if it returns
`Ok(())`

. Does nothing if capacity is already sufficient. This method
preserves the contents even if an error occurs.

##### Errors

If the capacity overflows, or the allocator reports a failure, then an error is returned.

##### Examples

```
use std::collections::BinaryHeap;
use std::collections::TryReserveError;
fn find_max_slow(data: &[u32]) -> Result<Option<u32>, TryReserveError> {
let mut heap = BinaryHeap::new();
// Pre-reserve the memory, exiting if we can't
heap.try_reserve(data.len())?;
// Now we know this can't OOM in the middle of our complex work
heap.extend(data.iter());
Ok(heap.pop())
}
```

Runsource#### pub fn shrink_to_fit(&mut self)

#### pub fn shrink_to_fit(&mut self)

1.56.0 · source#### pub fn shrink_to(&mut self, min_capacity: usize)

#### pub fn shrink_to(&mut self, min_capacity: usize)

Discards capacity with a lower bound.

The capacity will remain at least as large as both the length and the supplied value.

If the current capacity is less than the lower limit, this is a no-op.

##### Examples

```
use std::collections::BinaryHeap;
let mut heap: BinaryHeap<i32> = BinaryHeap::with_capacity(100);
assert!(heap.capacity() >= 100);
heap.shrink_to(10);
assert!(heap.capacity() >= 10);
```

Runsource#### pub fn as_slice(&self) -> &[T]

🔬This is a nightly-only experimental API. (`binary_heap_as_slice`

#83659)

#### pub fn as_slice(&self) -> &[T]

`binary_heap_as_slice`

#83659)1.6.0 · source#### pub fn drain(&mut self) -> Drain<'_, T> ⓘ

#### pub fn drain(&mut self) -> Drain<'_, T> ⓘ

Clears the binary heap, returning an iterator over the removed elements in arbitrary order. If the iterator is dropped before being fully consumed, it drops the remaining elements in arbitrary order.

The returned iterator keeps a mutable borrow on the heap to optimize its implementation.

##### Examples

Basic usage:

```
use std::collections::BinaryHeap;
let mut heap = BinaryHeap::from([1, 3]);
assert!(!heap.is_empty());
for x in heap.drain() {
println!("{x}");
}
assert!(heap.is_empty());
```

Run## Trait Implementations§

source§### impl<T: Clone> Clone for BinaryHeap<T>

### impl<T: Clone> Clone for BinaryHeap<T>

1.4.0 · source§### impl<T: Debug> Debug for BinaryHeap<T>

### impl<T: Debug> Debug for BinaryHeap<T>

source§### impl<T: Ord> Default for BinaryHeap<T>

### impl<T: Ord> Default for BinaryHeap<T>

source§#### fn default() -> BinaryHeap<T>

#### fn default() -> BinaryHeap<T>

Creates an empty `BinaryHeap<T>`

.

1.2.0 · source§### impl<'a, T: 'a + Ord + Copy> Extend<&'a T> for BinaryHeap<T>

### impl<'a, T: 'a + Ord + Copy> Extend<&'a T> for BinaryHeap<T>

source§### impl<T: Ord> Extend<T> for BinaryHeap<T>

### impl<T: Ord> Extend<T> for BinaryHeap<T>

source§#### fn extend<I: IntoIterator<Item = T>>(&mut self, iter: I)

#### fn extend<I: IntoIterator<Item = T>>(&mut self, iter: I)

source§#### fn extend_one(&mut self, item: T)

#### fn extend_one(&mut self, item: T)

`extend_one`

#72631)1.5.0 · source§### impl<T> From<BinaryHeap<T>> for Vec<T>

### impl<T> From<BinaryHeap<T>> for Vec<T>

source§#### fn from(heap: BinaryHeap<T>) -> Vec<T>

#### fn from(heap: BinaryHeap<T>) -> Vec<T>

Converts a `BinaryHeap<T>`

into a `Vec<T>`

.

This conversion requires no data movement or allocation, and has constant time complexity.

1.5.0 · source§### impl<T: Ord> From<Vec<T, Global>> for BinaryHeap<T>

### impl<T: Ord> From<Vec<T, Global>> for BinaryHeap<T>

source§#### fn from(vec: Vec<T>) -> BinaryHeap<T>

#### fn from(vec: Vec<T>) -> BinaryHeap<T>

Converts a `Vec<T>`

into a `BinaryHeap<T>`

.

This conversion happens in-place, and has *O*(*n*) time complexity.

source§### impl<T: Ord> FromIterator<T> for BinaryHeap<T>

### impl<T: Ord> FromIterator<T> for BinaryHeap<T>

source§#### fn from_iter<I: IntoIterator<Item = T>>(iter: I) -> BinaryHeap<T>

#### fn from_iter<I: IntoIterator<Item = T>>(iter: I) -> BinaryHeap<T>

source§### impl<'a, T> IntoIterator for &'a BinaryHeap<T>

### impl<'a, T> IntoIterator for &'a BinaryHeap<T>

source§### impl<T> IntoIterator for BinaryHeap<T>

### impl<T> IntoIterator for BinaryHeap<T>

source§#### fn into_iter(self) -> IntoIter<T> ⓘ

#### fn into_iter(self) -> IntoIter<T> ⓘ

Creates a consuming iterator, that is, one that moves each value out of the binary heap in arbitrary order. The binary heap cannot be used after calling this.

##### Examples

Basic usage:

```
use std::collections::BinaryHeap;
let heap = BinaryHeap::from([1, 2, 3, 4]);
// Print 1, 2, 3, 4 in arbitrary order
for x in heap.into_iter() {
// x has type i32, not &i32
println!("{x}");
}
```

Run