Update proposals/NNNN-global-actor-isolated-types-usability.md

simanerush · rjmccall · web-flow · commit 743c0721b18d · 2024-04-08T13:10:59.000-07:00
Co-authored-by: John McCall &lt;rjmccall@gmail.com&gt;
diff --git a/proposals/NNNN-global-actor-isolated-types-usability.md b/proposals/NNNN-global-actor-isolated-types-usability.md
@@ -138,7 +138,7 @@ func test(globallyIsolated: @escaping @MainActor () -> Void) {
 }
 ```
 
-The `globallyIsolated` closure in the above code is global-actor isolated via the `@MainActor`. Thus, it can never operate on the same reference concurrently at the same time, making it safe to be invoked from different isolation domains. This means that for such global-actor-isolated closures and functions, the `@Sendable` attribute is implicit.
+The `globallyIsolated` closure in the above code is global-actor isolated because it has the `@MainActor` attribute. Because it will always run isolated, it's fine for it to capture and use values that are isolated the same way. It's also safe to share it with other isolation domains because the captured values are never directly exposed to those isolation domains. This means that there's no reason not to always treat these functions as `@Sendable`.
 
 #### Non-`Sendable` captures in isolated closures
 

Original file line number	Diff line number	Diff line change
`@@ -138,7 +138,7 @@ func test(globallyIsolated: @escaping @MainActor () -> Void) {`
`138`	`138`	`}`
`139`	`139`	```
`140`	`140`
`141`		-The `globallyIsolated` closure in the above code is global-actor isolated via the `@MainActor`. Thus, it can never operate on the same reference concurrently at the same time, making it safe to be invoked from different isolation domains. This means that for such global-actor-isolated closures and functions, the `@Sendable` attribute is implicit.
	`141`	+The `globallyIsolated` closure in the above code is global-actor isolated because it has the `@MainActor` attribute. Because it will always run isolated, it's fine for it to capture and use values that are isolated the same way. It's also safe to share it with other isolation domains because the captured values are never directly exposed to those isolation domains. This means that there's no reason not to always treat these functions as `@Sendable`.
`142`	`142`
`143`	`143`	#### Non-`Sendable` captures in isolated closures
`144`	`144`