Skip to content

Commit 772d03c

Browse files
[SE-0461] Update remaining mentions of old feature name (#2856)
1 parent 747931e commit 772d03c

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

proposals/0461-async-function-isolation.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -204,7 +204,7 @@ actor MyActor {
204204

205205
Changing the default execution semantics of async functions can change the
206206
behavior of existing code, so the change is gated behind the
207-
`AsyncCallerExecution` upcoming feature flag. To help stage in the new
207+
`NonisolatedNonsendingByDefault` upcoming feature flag. To help stage in the new
208208
behavior, new syntax can be used to explicitly specify the
209209
execution semantics of an async function in any language mode.
210210

@@ -249,15 +249,15 @@ actor MyActor {
249249

250250
`@concurrent` is the current default for nonisolated async
251251
functions. `nonisolated(nonsending)` will become the default for async functions
252-
when the `AsyncCallerExecution` upcoming feature is enabled.
252+
when the `NonisolatedNonsendingByDefault` upcoming feature is enabled.
253253

254254
## Detailed design
255255

256256
The sections below will explicitly use `@concurrent` and
257257
`nonisolated(nonsending)` to demonstrate examples that will behave consistently
258258
independent of upcoming features or language modes. However, note that the
259-
end state under the `AsyncCallerExecution` upcoming feature will mean that
260-
`(nonsending)` is not necessary to explicitly write, and
259+
end state under the `NonisolatedNonsendingByDefault` upcoming feature will mean
260+
that `(nonsending)` is not necessary to explicitly write, and
261261
`@concurrent` will likely be used sparingly because it has far
262262
stricter data-race safety requirements.
263263

@@ -1119,8 +1119,8 @@ The proposal was revised with the following changes after the first review:
11191119

11201120
The proposal was revised with the following changes after the pitch discussion:
11211121

1122-
* Gate the behavior change behind an `AsyncCallerExecution` upcoming feature
1123-
flag.
1122+
* Gate the behavior change behind an `NonisolatedNonsendingByDefault` upcoming
1123+
feature flag.
11241124
* Change the spelling of `@concurrent` to `@execution(concurrent)`, and add an
11251125
`@execution(caller)` attribute to allow expressing the new behavior this
11261126
proposal introduces when the upcoming feature flag is not enabled.

0 commit comments

Comments
 (0)