Consistency of return value of ReadableStreamController method call on closed/errored streams

[tyoshino]

It's minor thing, but there's some inconsistency in the reference impl.

Currently:

• close() on a close()-ed stream: throw a TypeError saying it's already closed
• close() on an errored-before-close() stream: throw a TypeError saying it's errored
• enqueue() on an errored stream: throw a TypeError saying it's errored
• enqueue() on a close()-ed but not errored stream: throw a TypeError saying it's already closed

[domenic]

I don't actually understand the inconsistency. Is it about the presence or absence of the word "already"?

If it is just changing error message text, feel free to make the change (no PR needed).

[tyoshino]

Right, it's only about the ref impl. When one refers to it to know whether the difference of the order matters, they would notice that they have different messages and the two functions have different priorities and may have some question about that.

[tyoshino]

This has been fixed by e601d69

Now, for both ReadableStreamDefaultReader and ReadableStreamBYOBReader, close() and enqueue() has [[closeRequested]] check and [[state]] check in the same order.