Tracking Issue for `const_binary_heap_new_in`

[Coekjan]

Feature gate: #![feature(const_binary_heap_new_in)]

This is a tracking issue for constification of BinaryHeap::new_in, which allows user to create a BinaryHeap in compile-time with a specific allocator.

NOTE: This feature depends on the unstable feature allocator_api

Public API

impl<T: Ord, A: Allocator> BinaryHeap<T, A> {
    pub const fn new_in(alloc: A) -> BinaryHeap<T, A> {}
}

Steps / History

• Implementation: Mark constructor of BinaryHeap as const fn #117316
• Final comment period (FCP)
• Stabilization PR

Unresolved Questions

• None yet.

[RalfJung]

Given that this function is still unstable, and doesn't do anything that's particularly tricky from a const perspective, I don't think we need a separate feature gate. So closing in favor of #32838 which tracks all the new_in methods. (#133672 removes the feature gate from the code.)