Open
Description
This is a tracking issue for the change to call traits that are compatible with dyn
from "object safe" to "dyn compatible".
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
- Decide to do this.
- Update rustdoc.
- Update the compiler.
- Compiler: Rename "object safe" to "dyn compatible" #130826
- Compiler & its UI tests: Rename remaining occurrences of "object safe" to "dyn compatible" #131475
- Refactor dyn-compatibility error and suggestions #133372
- Compiler: Finalize dyn compatibility renaming #135860
- Update
compiler/rustc_codegen_cranelift
(out of tree, not in-tree) - Update
compiler/rustc_codegen_gcc
(out of tree, not in-tree)
- Update the standard library.
- Update the Reference.
- Update the dev guide.
- Update rust-analyzer.
- Update Miri.
- Update the Book?
- Update all open issues on this issue tracker (title, description).
- Fix all
FIXME(dyn_compat_renaming)
(mostly concerns URLs to the Reference). - Add an entry to the relnotes (
RELEASES.md
).
To do so, consider opening a new relnotes tracking issue with the relevant details.
cc @rust-lang/lang @fmease
Metadata
Metadata
Assignees
Labels
Area: Documentation for any part of the project, including the compiler, standard library, and toolsArea: Dyn compatibility (formerly: object safety)Category: An issue tracking the progress of sth. like the implementation of an RFCRelevant to the language team, which will review and decide on the PR/issue.