Re: [streams] How will ReadableByteStream work with seekable resources? (#253)

@domenic thanks for the clarification.

>From a ReadableByteStream POV, it is desirable to hide uncommitted data (a.k.a dirty read). So I think we should detach the given buffer. ArrayBuffer.transfer has been proposed to ES7, so we can use it when it gets stable enough. What do you think?

If we do so, the buffer returned by read is not the buffer we gave, regardless whether we use sync read + pull or async read.


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