Philippe Hausler

So the send returns in this case as soon as someone receives the value in an iterator. So it has the "async on both sides" behavior to ensure back pressure...

I think solutions in this territory are interesting; The one issue is that more often than not the buffer may be indefinite/unbounded. I think the uses are perhaps the important...

a stream from a large file should be pretty cheap; `AsyncBufferedByteIterator` is quite efficient and that type of strategy should be used to stream bytes. If the rate of one...

There are some unanswered questions with regards to sharing behaviors. For example; is it the best route to go having it be an "operator" style API? Combine takes the approach...

Perhaps the parts that we can help identify here are: what pieces do we need to build such a thing? And what are it's restrictions? First and foremost: any such...

One idea that I had a bit ago is to do something like this: ```swift @propertyWrapper public struct ThisDeservesABetterName { public private(set) var wrappedValue: Element let channel = AsyncChannel() public...

I think there are some expectations that may not meet. It should use back pressure not buffering: e.g. the next item should await all consumption of previous next calls to...

I agree that this is an important feature to iterate on (pun most assuredly intended). However the battle that we must face is that `share` in Combine feels a bit...

I'm out on vacation this week, but a few key points - merge (like all other algorithms) should only request the next value upon need/demand, I had a similar but...

One required item for merging this: it needs to definitely handle rethrowing cases (and we should validate that is true)