Undeprecated AsyncSequence erasing inits and methods #57
Conversation
This file contains hidden or 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
stephencelis
approved these changes
Jul 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR undeprecates the
initsanderasemethods that allow for converting an AsyncSequence into an AsyncStream or AsyncThrowingStream. These methods and inits were depracated in favor ofany AsyncSequence<Success, Error>.which can now be used in Swift 6. Dealing with such an async sequence introduces some complications, however. You can't just tack on operators likemaporfilteranymore like you can with anAsyncStream, and they require opening the underlying existential, which can be regarded as a pretty advanced and finicky area of the language.As such, it would be useful to have these inits and erase methods to be made available again, just from the perspective of ease of use.