Skip to content

Commit f76330d

Browse files
committed
burp 0.10
1 parent 9bedf55 commit f76330d

File tree

1 file changed

+7
-8
lines changed

1 file changed

+7
-8
lines changed

proposals/NNNN-migration-tooling-for-upcoming-features.md

+7-8
Original file line numberDiff line numberDiff line change
@@ -50,8 +50,8 @@ literal.
5050

5151
### Automation
5252

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:
5555

5656
* [`NonfrozenEnumExhaustivity`][SE-0192]: Restore exhaustivity with
5757
`@unknown default:`.
@@ -119,7 +119,7 @@ behavior in the *Source compatibility* section of the proposal.
119119
### Behavior
120120

121121
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.
123123
Additionally, this action will have no effect if the mode is not supported.
124124
A corresponding warning will be emitted in this case to avoid the false
125125
impression that the impacted source code is compatible with the feature.
@@ -233,9 +233,8 @@ SwiftSetting.enableUpcomingFeature("InternalImportsByDefault", mode: .adoption)
233233

234234
Diagnostics emitted in relation to a specific feature in adoption mode must
235235
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.
239238

240239
## Source compatibility
241240

@@ -271,8 +270,8 @@ Another potential direction for adoption mode is promotion of best practices.
271270

272271
The current serialization format for diagnostics does not include information
273272
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:
276275
* The diagnostic group name can be used to, well, group diagnostics, as well as
277276
to communicate relationships between diagnostics and features and filter out
278277
relevant diagnostics.

0 commit comments

Comments
 (0)