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

> We should strive to maintain our existing high test coverage where possible. #288 went through every test and rewrote it to work with an EOS read() design. I'm not sure that work is portable to { value, done } + read() only existing on a reader. But we'll need to do something similar.

Yeah. Let's use #288 for real work to be committed on the master. You've already done a lot there for async read() approach.

> I think I will try to stick with the same underlying source interface we have now for ReadableStream? However it might be better to build on top of #287's 

I'm seeing that the suitable underlying source interface and delegates would be a little different from markReadable, ... etc. when adopted async read() model. Let me continue the prototyping to see more detailed picture.

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