@@ -50,8 +50,8 @@ literal.
50
50
51
51
### Automation
52
52
53
- Many existing and prospective upcoming features imply or implement simple and
54
- consistent source modifications to facilitate adoption:
53
+ Many existing and prospective upcoming features come with simple and reliable
54
+ migration pathsimply to facilitate adoption:
55
55
56
56
* [ ` NonfrozenEnumExhaustivity ` ] [ SE-0192 ] : Restore exhaustivity with
57
57
` @unknown default: ` .
@@ -119,7 +119,7 @@ behavior in the *Source compatibility* section of the proposal.
119
119
### Behavior
120
120
121
121
The action of enabling a previously disabled source-breaking feature in adoption
122
- mode per se must not cause compilation errors .
122
+ mode per se must not cause compilation errors.
123
123
Additionally, this action will have no effect if the mode is not supported.
124
124
A corresponding warning will be emitted in this case to avoid the false
125
125
impression that the impacted source code is compatible with the feature.
@@ -233,9 +233,8 @@ SwiftSetting.enableUpcomingFeature("InternalImportsByDefault", mode: .adoption)
233
233
234
234
Diagnostics emitted in relation to a specific feature in adoption mode must
235
235
belong to a diagnostic group named after the feature. The names of diagnostic
236
- groups can be displayed along with diagnostic messages using
237
- ` -print-diagnostic-groups ` and can be used to associate a message with a
238
- particular feature.
236
+ groups can be displayed alongside diagnostic messages using
237
+ ` -print-diagnostic-groups ` and used to associate messages with features.
239
238
240
239
## Source compatibility
241
240
@@ -271,8 +270,8 @@ Another potential direction for adoption mode is promotion of best practices.
271
270
272
271
The current serialization format for diagnostics does not include information
273
272
about diagnostic groups or whether a particular fix-it preserves semantics.
274
- There are several reasons why this data is essential for future tools built
275
- around adoption mode:
273
+ There are several reasons why this data can be valuable for users, and why it
274
+ is essential for future tools built around adoption mode:
276
275
* The diagnostic group name can be used to, well, group diagnostics, as well as
277
276
to communicate relationships between diagnostics and features and filter out
278
277
relevant diagnostics.
0 commit comments