UncheckedSendable: AsyncSequence
#44
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, a non-sendable sequence cannot be erased to `AsyncStream` using this library's initializers even if one takes care to traffic it through via `nonisolated(unsafe)`: ```swift nonisolated(unsafe) let nonSendable = nonSendable AsyncStream(nonSendable) // 🛑 ``` This conditional conformance acts as a workaround: ```swift AsyncStream(UncheckedSendable(nonSendable)) ``` Ideally folks can stop using our concrete async sequence eraser in favor of `any AsyncSequence<Element, Failure>`, but this requires a minimum deployment target of iOS 18, so it won't be an option for many people for some time.
mbrandonw
approved these changes
Oct 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, a non-sendable sequence cannot be erased to
AsyncStreamusing this library's initializers even if one takes care to traffic it through vianonisolated(unsafe):This conditional conformance acts as a workaround:
Ideally folks can stop using our concrete async sequence eraser in favor of
any AsyncSequence<Element, Failure>, but this requires a minimum deployment target of iOS 18, so it won't be an option for many people for some time.