[Concurrency] Don't allow non-Sendable, isolated closures to capture non-Sendable values that may be isolated to a different actor.
#71536
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a closure is not
Sendable, its isolation differs from its enclosing context, and both contexts are actor isolated, treat the closure as if it may execute concurrently. Otherwise, the closure may capture non-Sendablestate from the outer context and stash it into isolated state on a different actor, allowing for concurrent access later on.See https://forums.swift.org/t/should-global-actor-isolated-functions-be-implicitly-sendable/60553/9 for more details.