-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Change the default edition for cargo new
to 2018
#5989
Conversation
As it says on the tin! Some tests were updated to explicitly pass 2015 so they can continue to work on stable, and otherwise `cargo new` should now by default generate a 2018 project.
r? @matklad (rust_highfive has picked a reviewer for you, use r? to override) |
@@ -75,7 +75,7 @@ fn both_lib_and_bin() { | |||
|
|||
#[test] | |||
fn simple_git() { | |||
cargo_process("new --lib foo").env("USER", "foo").run(); | |||
cargo_process("new --lib foo --edition 2015").env("USER", "foo").run(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it correct to assume these are temporary? I imagine in theory at least we'd want to not have this here -- most users shouldn't be passing/working in 2015 edition locally I imagine. Or, at least, we'd want tests for both.
Anyway, not a concern that needs to be resolved in this PR I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes these are temporary until the 2018 edition has hit the stable channel, and then we can change these tests back.
@bors r+ |
📌 Commit cf8d6a4 has been approved by |
Change the default edition for `cargo new` to 2018 As it says on the tin! Some tests were updated to explicitly pass 2015 so they can continue to work on stable, and otherwise `cargo new` should now by default generate a 2018 project.
☀️ Test successful - status-appveyor, status-travis |
As it says on the tin! Some tests were updated to explicitly pass 2015 so they
can continue to work on stable, and otherwise
cargo new
should now by defaultgenerate a 2018 project.