James M Snell

Let's close this in favor of the other proposal

Related: https://github.com/whatwg/streams/issues/1238

I'm happy with this approach also (in contrast to what I suggest in #1238). A key challenge I have with having these methods directly on `ReadableStream` is that they are...

All SGTM!

1. I prefer (a) as the end result. 2. I prefer (b) ... together at once 3. Given my answers to 1 and 2, I prefer we land a runtime...

The key ones with Promises would be: 1. Chains of purely synchronous Promise handlers. E.g. it would be interesting if we could detect and flag examples like `Promise(something).then(syncFunc).then(syncFun).then(syncFunc)....`. The way...

Not sure if we're going to go forward with this or not. There's more to figure out. But if we do move forward with this approach, the idea is to...

We've decided not to go this direction, thankfully :-)

Just spotted this, sorry for the late response. `WebSocketStream` is nicer and is definitely on my radar but I think it needs to bake a bit longer before we can...

As an alternative suggestion... consider adding this utility to the `streams/consumers` module and making it work with any `stream.Readable`, `ReadableStream`, and async iterable... ```js import { concat, arrayBuffer } from...