-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Tracking Issue for Transmutability Trait: #[transmutability] #99571
Copy link
Copy link
Open
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 RFCF-transmutability`#![feature(transmutability)]``#![feature(transmutability)]`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 RFCF-transmutability`#![feature(transmutability)]``#![feature(transmutability)]`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(transmutability)]This is a tracking issue for MCP411: Lang Item for Transmutability. The MCP defines an experimental, compiler-implemented trait that can be used to audit whether a particular transmutation (or other form of bit-reinterpretation cast) is safe.
At this time, this feature is NOT on track to stabilization. It has been specified in an MCP, not an RFC, and will likely require an RFC to be tracked for stabilization.
Public API
The public API of this feature (which may have evolved since this issue's last update), is roughly as follows:
Steps / History
Assumestruct to provide analysis options #100726Unresolved Questions
Virtually all aspects of this experimental feature are unresolved.
Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩