Re: [streams] Support reading bytes into buffers allocated by user code on platforms where only async read is available (#253)

> I think it should still return ReadableStream.EOS, not an empty buffer.

OK but need to return the detached ArrayBuffer. The empty view holds the detached ArrayBuffer.

> "Readable streams" have pipeTo and pipeThrough methods, and probably a closed promise, and maybe a cancel() method. But they do not have a direct read() method.
> "Readable streams" let you get "readers" which have direct read() methods. (Maybe readers should have the rest of the readable stream interface too. Or maybe not.)

That's what we planned. I wanted to say we standardize pipeTo but it's not on the object from which we can read().

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/253#issuecomment-77455696