This is a proposal to add asyncStream and asyncThrowingStream in order to bridge into Swift Concurrency. I find this especially useful for writing non-blocking async tests.

A couple of things I'd love to hear your thoughts on (apart from the usual review):

• General thoughts on the idea
• Where to place these extensions within the project and naming of files
• Raising of CI platform to Xcode 11 (due to minimum Swift and testing target version requirements)
• Lack of support for Swift Concurrency in Quick/Nimble (leading to tests written with XCTest)

Note: Mac Catalyst builds are failing to launch on pre-monterey macOS versions: There is a workaround described in the documents but probably not worth implementing in the CI. More info here.

Mac Catalyst apps that use Swift Concurrency may fail to launch on an operating system prior to macOS Monterey. (84393581)

This is a proposal to add asyncStream and asyncThrowingStream in order to bridge into Swift Concurrency. I find this especially useful for writing non-blocking async tests.

A couple of things I'd love to hear your thoughts on (apart from the usual review):

• General thoughts on the idea
• Where to place these extensions within the project and naming of files
• Raising of CI platform to Xcode 11 (due to minimum Swift and testing target version requirements)
• Lack of support for Swift Concurrency in Quick/Nimble (leading to tests written with XCTest)

Note: Mac Catalyst builds are failing to launch on pre-monterey macOS versions: There is a workaround described in the documents but probably not worth implementing in the CI. More info here.

Mac Catalyst apps that use Swift Concurrency may fail to launch on an operating system prior to macOS Monterey. (84393581)