The first thing I was about to comment was "how does one handle backpressure with this library?" Thankfully the examples given in the repository demonstrate exactly that :)

I still think it'd be useful to mention in the README what the library offers for dealing with backpressure. e.g. does the library offer dropping buffers, sliding buffers, ...? Probably after the README example demonstrating how to create a channel that can receive exactly two values.

Stunned but not surprised how badly Swift's built-in async channels package performs compared to Go. Consistently more than an order of magnitude worse.

I really like the idea, I’m not sure I love the use of operators over named functions.

Could named functions be a optional alternative API?

Nice, now I can have the nice concurrency syntax with the error handling I know and love. ♡