Re: [whatwg/streams] pipeTo() algorithm shuts down too early on readable close()? (#644)

> For the Chromium implementation, I'm thinking of removing the 'Wait until any ongoing write finishes (i.e. the corresponding promises settle).' step from 'shutdown with action' because now that we treat underlying sink write() as uninterruptible it doesn't make any difference any more, and that step is troublesome to implement. Maybe we should also remove it from the standard?

Yeah, that sounds good to me, as long as the sanity test of removing its implementation from the reference implementation doesn't cause any test failures.

I guess it would be observably different in that the readable stream might become canceled sooner. Which is probably a good thing.

-- 
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/issues/644#issuecomment-272769605