Tracking issue for RFC 3722: Explicit ABIs in `extern`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
This is a tracking issue for:
The feature gate for the issue is #![feature(explicit_extern_abis)].
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
- Accept an RFC.
- Add migration lint.
- Make and FCP the change to warn-by-default in all editions.
- Make this a hard error in the next edition on nightly under a feature flag.
- Blocked on finalizing the name and timing of the next edition.
- https://github.com/rust-lang/rust/pull/135340
- Add documentation to the dev guide.
- See the instructions.
- Add documentation to the reference.
- See the instructions.
- Add formatting for new syntax to the style guide.
- See the nightly style procedure.
- Stabilize on nightly on the next edition.
- See the instructions.
Unresolved Questions
None.
Related
TODO.
Implementation history
TODO.
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 with the linked RFC 3722 and the rustc-dev-guide stabilization instructions, then review the remaining checklist items for dev guide, reference, and style-guide documentation. The work is done when the outstanding documentation and formatting tasks are completed and the feature reaches the listed stabilization step; the next-edition error remains blocked by edition naming and timing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100