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

I was on vacation and didn't have time to do it, sorry. Thanks so much for great progress!

> I guess part of the reason I have it is that it's better to avoid forcing people to use try/catch.

Oh, I see. I'm now a little inclined to keep it.

> I said releaseLock() since ...

Got it!

> the check source.state === "closed" never works

Thanks for explanation. I understand and agree that it makes sense for transition-to-"closed" case.

When a reader is unlocked while the associated stream is readable/waiting, it's a bit weird to keep exposing the non-closed stream's status via the released reader. What do you think about making a reader look like a closed stream regardless for what kind of transition the unlock happened?

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