Re: [whatwg/streams] define semantics of {source,sink}.finally() (#636)

I think sometimes we will need to call finally() asynchronously because we are in a bad state and can't deal with re-entrancy issues. It might be good to guarantee that we always call finally() asynchronously, so that sink code can be sure that none of its own code is executing synchronously. On the other hand, it may be sufficient to guarantee that none of the sink methods are on the stack.

Everything applies the same to ReadableStream and TransformStream. WritableStream is just what's on my mind right now.

-- 
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/636#issuecomment-278895123