Tracking Issue for `BinaryHeap::as_mut_slice`
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_as_mut_slice)]
This is a tracking issue for BinaryHeap::as_mut_slice function. This function returns a mutable slice of all values in the underlying vector of the binary heap.
Public API
impl<T, A: Allocator> BinaryHeap<T, A> {
pub unsafe fn as_mut_slice(&mut self) -> &mut [T];
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: https://github.com/rust-lang/libs-team/issues/756
- Implementation: https://github.com/rust-lang/rust/pull/154011
- 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 by reviewing the ACP at rust-lang/libs-team#756 and the implementation PR rust-lang/rust#154011, then read the linked stabilization guidance. The tracking work is done when the final comment period concludes and a stabilization PR is opened and completed.
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