-
-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Tracking Issue for ManuallyDrop<T>::pinned_* #157268
Copy link
Copy link
Closed as not planned
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-unimplementedStatus: The feature has not been implemented.Status: The feature has not been implemented.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-unimplementedStatus: The feature has not been implemented.Status: The feature has not been implemented.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Feature gate:
#![feature(manually_drop_pinned)]This is a tracking issue for rust-langs/libs-team#580. It introduces a few methods to
ManuallyDrop<T>for the purpose of constructing a new mutable/immutablePinoverTout ofPin<&mut ManuallyDrop<T>>andPin<&ManuallyDrop<T>>as well as be able to drop pinned contained values.Public API
Steps / History
(Remember to update the
S-tracking-*label when checking boxes.)ManuallyDrop<T>::pinned_*methods libs-team#580ManuallyDrop<T>::pinned_*methods #157269Unresolved Questions
Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩