From 80ee30d9234239c7cbaf22e65019d087c3e73d93 Mon Sep 17 00:00:00 2001 From: Josh Triplett Date: Wed, 16 Nov 2022 17:00:30 -0800 Subject: [PATCH] Discuss permanent vs temporary use of old style editions --- text/3338-style-evolution.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/text/3338-style-evolution.md b/text/3338-style-evolution.md index d52b018d7af..ddc4eedee2d 100644 --- a/text/3338-style-evolution.md +++ b/text/3338-style-evolution.md @@ -87,6 +87,17 @@ for handling forwards-compatibility and wonder how they differ. We feel that since we're providing a mechanism similar to editions, we should make it clear to users that it works like editions. +We could allow style edition to vary completely independently of Rust edition. +This would, for instance, allow projects to stay on old style editions +indefinitely. However, this would substantially increase the development and +testing burden for formatting tooling, and require more complex decisions about +how old style editions format constructs that didn't exist in the corresponding +Rust edition. In general, while the Rust edition mechanism allows projects to +stay on old Rust editions, and projects doing so can similarly stay on the +corresponding old style editions, the style edition mechanism does not exist to +facilitate staying on old styles *indefinitely* while still moving forward to +newer Rust editions. + We could leave out the separate configuration of style edition, and keep style edition in lockstep with Rust edition. This would be easier to develop and test, but would mean larger and noisier commits in projects transitioning from