-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking Issue for MaybeDangling #118166
Comments
@rust-lang/opsem I realized we probably should have included t-opsem in the FCP for this RFC. Let's try to remember to do a t-opsem FCP in the PR with the initial implementation, just to make sure the team is on board. |
There's an interesting open question I did not realize about the exact validity of |
This is a tracking issue for the experimental MaybeDangling type (as per the T-lang experimental feature process). The type is described by this RFC, but we can experiment with adding the type unstably (and even using it in
ManuallyDrop
) before the RFC gets accepted.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
MaybeDangling
references?(see RFC)
Implementation history
The text was updated successfully, but these errors were encountered: