Tracking Issue for `BinaryHeap::from_raw_vec`
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(binary_heap_from_raw_vec)]
This is a tracking issue for the BinaryHeap::from_raw_vec function. This function constructs a BinaryHeap from a Vec without performing a heapify.
Public API
impl <T, A: Allocator> BinaryHeap<T, A> {
pub unsafe fn from_raw_vec(vec: Vec<T, A>) -> BinaryHeap<T, A>
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: rust-lang/libs-team#710
- Implementation: #152502
- 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
Review the completed ACP and implementation PR #152502, then read the feature-lifecycle stabilization guidance linked in the issue. The remaining work is the final comment period and a stabilization PR; no implementation task, file, or test is specified here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100