Tracking Issue for RFC 3325: unsafe attributes #123757
Labels
A-edition-2024
Area: The 2024 edition
B-RFC-approved
Blocker: Approved by a merged RFC but not yet implemented.
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
I-style-nominated
The issue / PR has been nominated for discussion during a style team meeting.
S-tracking-impl-incomplete
Status: The implementation is incomplete.
S-tracking-needs-documentation
Status: Needs documentation.
S-tracking-needs-migration-lint
Status: This item needs a migration lint.
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
This is a tracking issue for RFC 3325: unsafe attributes
The feature gate for the issue is
#![feature(unsafe_attributes)]
.About tracking issues
Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
Unresolved Questions
no_mangle
outsideunsafe(...)
could be staged in various ways: it could be warn-by-default to start or we wait a while before to do that, it could be edition-dependent, it might eventually be deny-by-default or even a hard error on some editions -- there are lots of details here, which can be determined later during the process.Implementation history
cc @RalfJung @carbotaniuman @rust-lang/style
This issue has been assigned to @carbotaniuman via this comment.
The text was updated successfully, but these errors were encountered: