Concurrency: add missing Sendable requirements, conformances, and address other warnings #39062
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.
A few fixes to the concurrency library that address warnings:
Sendable
constraint toMainActor.run
and a few of the back-deployment shims._AsyncStreamCriticalStorage
conform toSendable
(this is@unchecked
because it's a class that handles its own locking)._runAsyncMain
take an@_unsafeSendable
parameter. There's a compiler bug here still, which results in a spurious warning.AsyncStream
implementation over towithTaskCancellationHandler
.