[5.10][Concurrency] An assortment of bug fixes in Sendable and actor isolation checking.
#68852
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.
nonisolatedinitializer of a subclass could invoke global-actor-isolated properties in the superclass.Sendablechecking for function references where parameter and result types wereSendable-checked at the point of partial application when there was no function conversion. Sendability of function references depends only on captures, and applies when the function itself is passed across isolation boundaries. Parameter and result values can only cross isolation boundaries when the function is called, so they shouldn't be checked when checking a reference for Sendable violations.This change also includes a minor refactoring to consolidate the representation of actor isolation across function declarations and closures.
test/Concurrency/.ClosureActorIsolation. #68567