Re: [streams] Should we "lock" readable streams while piping? (#241)

Having piping built in to the stream sounds tempting for some performance cases but it's only going to work if it can take a user specified read method and just make it private for use but the internal pipeing. There's all kinds of reasons you need to customize or wrap the read function. I do it in almost every new style stream I've written, usually to do lazy completion and state checking the first time read() is called.

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