Franz Busch

We clarified the behaviour of send in the recent doc update: > /// Sends an element to an awaiting iteration. This function will resume when the next call to `next()`...

We removed `Task.select` since it encouraged the usage of unstructured concurrency; hence, closing this issue.

@phausler can we close this in favour of: https://github.com/apple/swift-async-algorithms/pull/297

`AsyncSequence` the primary building block of this package is using a pull based eventing approach whereas `Combine` uses a push based model. The other difference here is that `AsyncSequence` are...

> > Combine uses a push based model. > > > > No; this is not true - Combine uses a demand based model; everything is pull based. I was...

CI is now setup for the latest nightly Swift versions. So let's close this.

IMO the current semantics fit very well with what we want to achieve with this type. The intention is to have a multi-producer multi-consumer root asynchronous sequence that allows lock-step...

@phausler I think we can close this issue now?

I am closing this PR for now since `AsyncChannel` has since been reimplemented.

@phausler Should we reconsider the naming here?