Re: [whatwg/streams] Fix typo in Close/Enqueue checks for readable byte streams (#1051)

> I might be going on a bit of a tangent here, but... Now that ReadableStreamDefaultControllerEnqueue no longer asserts CanCloseOrEnqueue() but instead early-returns, shouldn't we do the same thing for TransformStreamDefaultControllerEnqueue?

I think it's less clear-cut for TransformStreamDefaultControllerEnqueue because it is already handling the exceptional case, so there is no danger of state confusion. I don't feel strongly that we need to be consistent here.

-- 
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/1051#issuecomment-654262464