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

Makes sense, although I will need to try validating to make sure that things like

> When a reader other than ReadableStream's is released, ReadableStream's reader will be locked again automatically.

Are doable in a sane way, and to figure out the "not sure" things. Will try to do so Monday.

> When a reader is released, its .state returns "locked by someone". 

I think "waiting" works fine, as the observable behavior is the same---you cannot read or see anything happen until `.ready` fulfills.

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