Skip to content
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 "Overconstraining and omitting unsafe in impls of unsafe trait methods" (RFC 2316) #87919

Closed
3 tasks
scottmcm opened this issue Aug 10, 2021 · 3 comments
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC S-tracking-impl-incomplete Status: The implementation is incomplete. T-lang Relevant to the language team, which will review and decide on the PR/issue.

Comments

@scottmcm
Copy link
Member

This is a tracking issue for the RFC "Overconstraining and omitting unsafe in impls of unsafe trait methods" (rust-lang/rfcs#2316).
The feature gate for the issue is #![feature(⚠ not yet chosen ⚠)].

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

None known at this time

Implementation history

@scottmcm scottmcm added T-lang Relevant to the language team, which will review and decide on the PR/issue. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC labels Aug 10, 2021
@joshtriplett joshtriplett added the S-tracking-impl-incomplete Status: The implementation is incomplete. label Jul 27, 2022
@tmandry
Copy link
Member

tmandry commented Aug 18, 2022

This RFC was revised and generalized by rust-lang/rfcs#3245, which is now tracked in #100706.

@clarfonthey
Copy link
Contributor

Should this be closed if it's superceded by a more general RFC? Or will this just track implementing it for unsafety specifically?

@Dylan-DPC
Copy link
Member

Closing this as #100706 tracks this.

@Dylan-DPC Dylan-DPC closed this as not planned Won't fix, can't repro, duplicate, stale Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC S-tracking-impl-incomplete Status: The implementation is incomplete. T-lang Relevant to the language team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

5 participants