Tracking Issue for const `ManuallyDrop::take` (`const_manually_drop_take`)
Open
Nobody has claimed this yet.
C-tracking-issue
S-tracking-ready-to-stabilize
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(const_manually_drop_take)]
This is a tracking issue for const ManuallyDrop::take.
Public API
// core::mem::manually_drop
impl<T> ManuallyDrop<T> {
pub const unsafe fn take(slot: &mut ManuallyDrop<T>) -> T;
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- Implementation: #148752
- 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 implementation PR #148752 and the public API for ManuallyDrop::take in the issue. Read the linked stabilization guide to understand the remaining FCP and stabilization steps; the issue is complete when those checklist items are resolved and the API is stabilized.
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
- Needs clarification
- Newbie friendliness
- 20/100