Tracking Issue for RFC 3855
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
This is a tracking issue for the RFC "3855" (rust-lang/rfcs#3855).
The feature gate for the issue is #![feature(mitigation_enforcement)].
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.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.
Steps
- Implement the RFC (cc @arielb1 @rust-lang/project-exploit-mitigations )
- Adjust documentation (see instructions on rustc-dev-guide)
- Stabilization PR (see instructions on rustc-dev-guide)
Unresolved Questions
None.
Implementation history
- https://github.com/rust-lang/rust/pull/146369 (not implementation, but related/originated the RFC discussions)
- https://github.com/rust-lang/rust/pull/149357
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading RFC 3855 and the rustc-dev-guide documentation and stabilization instructions linked in the issue. Review the completed implementation and the remaining checklist items; done means a documentation PR and a stabilization PR for the mitigation_enforcement feature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100