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

simanerush · rjmccall · web-flow · commit ea1dac0a4d90 · 2024-04-05T23:47:26.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
@@ -48,7 +48,6 @@ func test() {
 }
 ```
 
-Requiring both a global actor attribute and `@Sendable` creates an unfortunate pile-up of attributes, and it would be better to infer `@Sendable` from the global actor attribute.
 
 Because a globally-isolated closure cannot be called concurrently, it's safe for it to capture non-`Sendable` values even if it's implicitly `@Sendable`.  Such values just need to be transferred to the global actor's region (if they aren't there already).  The same logic also applies to closures that are isolated to a specific actor reference, although it isn't currently possible to write such a closure in a context that isn't isolated to that actor.
 

Original file line number	Diff line number	Diff line change
`@@ -48,7 +48,6 @@ func test() {`
`48`	`48`	`}`
`49`	`49`	```
`50`	`50`
`51`		-Requiring both a global actor attribute and `@Sendable` creates an unfortunate pile-up of attributes, and it would be better to infer `@Sendable` from the global actor attribute.
`52`	`51`
`53`	`52`	Because a globally-isolated closure cannot be called concurrently, it's safe for it to capture non-`Sendable` values even if it's implicitly `@Sendable`. Such values just need to be transferred to the global actor's region (if they aren't there already). The same logic also applies to closures that are isolated to a specific actor reference, although it isn't currently possible to write such a closure in a context that isn't isolated to that actor.
`54`	`53`