- From: Takeshi Yoshino <notifications@github.com>
- Date: Thu, 26 Jan 2017 00:16:25 -0800
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 26 January 2017 08:16:56 UTC
tyoshino commented on this pull request. > @@ -2932,6 +2924,15 @@ nothrow>WritableStreamFinishPendingCloseWithError ( <var>stream</var>, <var>reas 1. Perform ! WritableStreamRejectClosedPromiseIfAny(_stream_). </emu-alg> +<h4 id="writable-stream-is-ready-promise-pending" aoid="WritableStreamIsReadyPromisePending" +nothrow>WritableStreamIsReadyPromisePending ( <var>stream</var>, <var>state</var>, <var>wasAborted</var> )</h4> Thanks. I'll use WritableStreamIsReadyForWrites. Do you think IsWritableStreamReadyForWrites better? > @@ -2932,6 +2924,15 @@ nothrow>WritableStreamFinishPendingCloseWithError ( <var>stream</var>, <var>reas 1. Perform ! WritableStreamRejectClosedPromiseIfAny(_stream_). </emu-alg> +<h4 id="writable-stream-is-ready-promise-pending" aoid="WritableStreamIsReadyPromisePending" +nothrow>WritableStreamIsReadyPromisePending ( <var>stream</var>, <var>state</var>, <var>wasAborted</var> )</h4> + +<emu-alg> Yeah, good point. The new function should just look at `stream`, and it should be placed at some safe place before updating the state variables. Will fix. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/pull/671
Received on Thursday, 26 January 2017 08:16:56 UTC