-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Tracking issue for Transitioning crates to Rust 2018 #58099
Copy link
Copy link
Closed
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.WG-epochWorking group: Epoch (2018) managementWorking group: Epoch (2018) management
Metadata
Metadata
Assignees
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.WG-epochWorking group: Epoch (2018) managementWorking group: Epoch (2018) management
Type
Fields
Give feedbackNo fields configured for issues without a type.
This issue tracks the transitioning of all crates in this repo and sub-modules to Rust 2018.
You can help by filing PRs transitioning a crate at a time to Rust 2018.
When transitioning, please apply the following to the crate root:
You can try to use
cargo +nightly fix(orcargo +nightly --edition-idioms) to migrate a crate automatically; see the edition guide for details. However, due to bootstrapping, you might need to do some manual intervention here and there.If you want to help out, please pick a crate and leave a comment here.
When you make a transitioning PR, also leave a comment here.
cc @rust-lang/compiler @rust-lang/infra
The following crates exist in the repo or as submodules.
Checked items have been transitioned to Rust 2018.