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

I think I would punt on the issue and just stick to async read for now. `readInto` is useful only for performance reasons; it enables nothing that couldn't be done with an async `read(bytes)`. So you might as well wait and get feedback from users (on use cases) and implementers (on optimization constraints). 

@indutny's use case is fair, but that's only because openssl API limitations.
It's easy to think of alternative solutions though - read into an abstract buffer that whose contents are not accessible from js, for example.

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