Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[SR-14945] AsyncThrowingStream.init(unfolding:) can throw errors other than Failure type #57287

Closed
stephencelis opened this issue Jul 20, 2021 · 2 comments
Closed

[SR-14945] AsyncThrowingStream.init(unfolding:) can throw errors other than Failure type #57287

stephencelis opened this issue Jul 20, 2021 · 2 comments
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. standard library Area: Standard library umbrella

Comments

@stephencelis
Copy link
Contributor

Previous ID SR-14945
Radar rdar://problem/80970499
Original Reporter @stephencelis
Type Bug
Status Resolved
Resolution Done
Environment

Swift 5.5 (Xcode beta 3)

Additional Detail from JIRA
Votes 0
Component/s Standard Library
Labels Bug
Assignee None
Priority Medium

md5: 45c0f634928a812ff1b80bd07f4730e0

Issue Description:

AsyncThrowingStream.init(unfolding🙂 takes a throwing closure but is not constrained in its Failure type, which means it's possible to create an AsyncThrowingStream that throws an error other than its Failure type. It should probably be constrained where Failure == Error, like its other initializer.
@stephencelis
Copy link
Contributor Author

#38506

@DougGregor
Copy link
Member

@swift-ci create

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. standard library Area: Standard library umbrella
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stephencelis @DougGregor