Stefan

A few questions (about the Async interfaces, I didn't look much into the implementations): 1. Isn't this missing the cancellationtoken and if yes, you probably need that special attribute ``...

Thank you for your detailed answer and I think it dawned on me, the consumer never ever implements these interfaces, he only **consumes** them, right? I looked at these interfaces,...

Ah yes, I forgot ``ArraySegment``, the ugly stepchild of array that existed for aeons but was pretty much unused until the whole ArrayPool and Span/Memory story started. I unfortunately don't...

> The symmetry is desirable for one, but I also worry that it'd frustrate clients converting sync paths to async ones. Thoughts? I agree, keeping it both is preferable then.

Nice, I see similar improvements with my use case and your changes.

Honestly I'm surprised that IAsyncEnumerable works at all.

IAsnycEnumerable only works properly if you have a full async pipeline. I guess that in 5.0 it was actually sync or fully synchronously buffered and in 6.0 it's not anymore.

It would be quite useful if you could provide a repro for your problem, this problem is likely dependent on one of the concrete types.

Okay, you still return IAsnycEnumerable, I was confused as you wrote about Ienumerable in between. As I previously said, this can't work properly.

Yes, you need to drain the pipeline fully at the moment. Support for this is probably part of async support as that's basically necessary for ``Pipeline`` support. Unfortunately async/await support...