Skip to content

Commit 27f8cc6

Browse files
doozMenktoso
authored andcommitted
Update 0424-custom-isolation-checking-for-serialexecutor.md
Typo fix
1 parent ab898ce commit 27f8cc6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

proposals/0424-custom-isolation-checking-for-serialexecutor.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -165,7 +165,7 @@ actor Worker {
165165

166166
As such, there is no negative impact on the correctness of these APIs.
167167

168-
Asynchronous functions should not use dyanamic isolation checking. Isolation checking is useful in synchronous functions because they naturally inherit execution properties like their caller's isolation without disturbing it. A synchronous function may be formally non-isolated and yet actually run in an isolated context dynamically. This is not true for asynchronous functions, which switch to their formal isolation on entry without regard to their caller's isolation. If an asynchronous function is not formally isolated to an actor, its execution will never be dynamically in an isolated context, so there's no point in checking for it.
168+
Asynchronous functions should not use dynamic isolation checking. Isolation checking is useful in synchronous functions because they naturally inherit execution properties like their caller's isolation without disturbing it. A synchronous function may be formally non-isolated and yet actually run in an isolated context dynamically. This is not true for asynchronous functions, which switch to their formal isolation on entry without regard to their caller's isolation. If an asynchronous function is not formally isolated to an actor, its execution will never be dynamically in an isolated context, so there's no point in checking for it.
169169

170170
## Future directions
171171

0 commit comments

Comments
 (0)