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

One concern about (C) is that people may be impressed that calling multiple pull()s is harmless when using object streams, and may call many pull()s without being aware of internal allocation of ArrayBuffer and kicking read. Naming it pull() than wait() gives some notion of side-effect, but still weak?

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