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`? That means:
* Move what is currently [step 3 of `TransformStreamDefaultControllerEnqueue`](https://streams.spec.whatwg.org/commit-snapshots/c63ae9eb7de6069f0e3cf5ea6b0ef68a2c8a3971/#set-up-transform-stream-default-controller-enqueue) into [`TransformStreamDefaultController.enqueue()`](https://streams.spec.whatwg.org/commit-snapshots/c63ae9eb7de6069f0e3cf5ea6b0ef68a2c8a3971/#ts-default-controller-enqueue).
* Add a check + early-return at the start of `TransformStreamDefaultControllerEnqueue`.

(Even more of a tangent: I just noticed that the anchor links for these transform stream abstract ops are weird. For example, `TransformStreamDefaultControllerEnqueue` is linked as `#set-up-transform-stream-default-controller-enqueue`. The `set-up-` bit looks like a copy-paste error? 😅)

-- 
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-653949562