Skip to content

Commit 80ee30d

Browse files
committed
Discuss permanent vs temporary use of old style editions
1 parent 51ec872 commit 80ee30d

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

text/3338-style-evolution.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,17 @@ for handling forwards-compatibility and wonder how they differ. We feel that
8787
since we're providing a mechanism similar to editions, we should make it clear
8888
to users that it works like editions.
8989

90+
We could allow style edition to vary completely independently of Rust edition.
91+
This would, for instance, allow projects to stay on old style editions
92+
indefinitely. However, this would substantially increase the development and
93+
testing burden for formatting tooling, and require more complex decisions about
94+
how old style editions format constructs that didn't exist in the corresponding
95+
Rust edition. In general, while the Rust edition mechanism allows projects to
96+
stay on old Rust editions, and projects doing so can similarly stay on the
97+
corresponding old style editions, the style edition mechanism does not exist to
98+
facilitate staying on old styles *indefinitely* while still moving forward to
99+
newer Rust editions.
100+
90101
We could leave out the separate configuration of style edition, and keep style
91102
edition in lockstep with Rust edition. This would be easier to develop and
92103
test, but would mean larger and noisier commits in projects transitioning from

0 commit comments

Comments
 (0)