Skip to content

Edition 2021 and beyond #2966

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.

Sign up for GitHub

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

Closed
wants to merge 16 commits into from
Closed

Edition 2021 and beyond #2966

Changes from 1 commit
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
7464420
Edition 2021 and beyond, draft 1
nikomatsakis Jul 28, 2020
f30e7fe
fix RFC 2795 link
nikomatsakis Jul 29, 2020
09bc9a3
fix typos
nikomatsakis Jul 29, 2020
7ef2476
reword to avoid suggesting a specific list of questions
nikomatsakis Jul 29, 2020
b1fc149
s/migate/migrate/
nikomatsakis Jul 30, 2020
ebf2b49
remove discussion of "celebratory affair"
nikomatsakis Sep 21, 2020
235bd82
clarify lint policy
nikomatsakis Sep 21, 2020
3b57d66
clarify limited role of edition guide
nikomatsakis Sep 21, 2020
8cded7b
remove discussion of project group
nikomatsakis Sep 21, 2020
012dd80
clarify editions and semver
nikomatsakis Sep 21, 2020
8c12c54
clarify semver more
nikomatsakis Sep 21, 2020
3cc771e
fix typos
nikomatsakis Sep 22, 2020
0a4b1ed
pull out the note about leveraging editions for complex refactorings
nikomatsakis Sep 27, 2020
abe46e7
clarify that an "empty edition" is an unresolved question
nikomatsakis Sep 27, 2020
329cbe0
clarify migration/idiom-lint policy
nikomatsakis Sep 27, 2020
178e646
Update text/0000-edition-2021-and-beyond.md
nikomatsakis Sep 30, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions text/0000-edition-2021-and-beyond.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,9 +92,9 @@ The aim of the edition guide is to help users who are migrating code from one ed

## Editions and semver

For semver purposes, you should think of editions as being equivalent to any other Rust feature. If Edition N is stabilized in rustc release 1.X, then upgrading your crate to edition N also means that your crate can only be compiled with rustc release 1.X. This is no different than if you added a use of some other new feature that was added in release 1.X but which is not tied to editions.
For semver purposes, you should think of editions as being equivalent to any other Rust feature. If Edition N is stabilized in rustc release 1.X, then upgrading your crate to edition N also means that your crate can only be compiled with rustc release 1.X or later. This is no different than if you added a use of some other new feature that was added in release 1.X but which is not tied to editions.

Rust does not have an official policy on whether it is a semver breaking change to depend on new features, but most crates do establish a policy that they maintain individually. Therefore, adopting a new edition is a breaking if and only if your crate considers it a breaking change to depend on the Rust compiler release that supports that edition.
Rust does not have an official policy on whether it is a semver breaking change to change the version of the Rust compiler required to compile your crate. In practice, widely used crates generally adoptand document a "MSRV" (Minimum Supported Rust Version) and have rules about when it can be changed. Upgrading to an edition may then trigger a change to the MSRV and hence could be considered a breaking change, depending on the crate's policy.

# Reference-level explanation
[reference-level-explanation]: #reference-level-explanation
Expand Down