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

At this point I am tempted to go back to my original idea of [[piping]] built in to the stream. It would cause .read() to throw, .state to return "waiting", and .ready to return a promise that is fulfilled when the piping is over and the stream becomes readable or closed (perhaps errored too, given #245). Everything else seems over-engineered. Which would be OK if the user-facing ergonomics were worth it, but I am not sure that they are.

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