- From: Domenic Denicola <notifications@github.com>
- Date: Tue, 18 Aug 2015 14:43:13 -0700
- To: whatwg/streams <streams@noreply.github.com>
Received on Tuesday, 18 August 2015 21:43:42 UTC
OK, I have pushed to this PR with a base commit that removes automatic unlocking on close/error. Two important questions: - Should we now reject read() and closed when used on released readers, instead of treating as a closed/errored stream? That seems simpler. - **Are we OK with breaking compat on this?** It would be a breaking change to Chrome's current behavior, and a change in an area of the spec we've called stable. I personally think it is unlikely to break things, but what do you think? /cc @yutakahirano @calvaris --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/pull/385#issuecomment-132364121
Received on Tuesday, 18 August 2015 21:43:42 UTC