Re: [whatwg/streams] Brainstorming a buffer-reusing version of writable streams (#495)

Another option is to have no special optimised byte Writer at all. If you wanted optimal behaviour you would create a byte ReadableStream and pipe that to the byte WritableStream. pipeTo() would do some magic (possibly unspecified?) to minimise allocations and copies.

Okay, "unspecified magic" would violate predictability. Make it "specified magic".

To put it another way, pipeTo() has to be as efficient as we can make it. So the minimum criteria for having a specialised byte Writer should be either that it is easier to use than `new ReadableStream({pull() { ... }, type: 'bytes'}).pipeTo(byteWritable)`, or that it is more efficient.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/495#issuecomment-283266179