Re: [streams] Maybe giving async readInto (and read?) another shot (#290)

Yeah I don't think it's going to be possible to have a readInto that allows @indutny's use case to be replicated in JS without shared memory :(. And that is blocked on a lot more than me (although I guess io.js Buffers are shared, so there's a loophole for io at least).

The question is whether there is sufficient use case left for a transfer-based readInto, even though it would not be able to address @indutny's use case. The long linked gist has some that basically boil down to "avoid memory fragmentation", when compared with pull(buff_opt) + sync read(). I'm not sure those are enough.

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