Re: [whatwg/streams] Editorial: add cross-links to internal slots (#1050)

Unfortunately, it's not *just* this one case. All of the following abstract ops can be called on both types of readers. As such, (1) is not an option:
* `ReadableStreamReaderGenericInitialize` uses both _reader_.[[stream]] and _reader_.[[closedPromise]]
* `ReadableStreamReaderGenericRelease` uses both _reader_.[[stream]] and _reader_.[[closedPromise]]
* `ReadableStreamClose` uses _reader_.[[closedPromise]]
* `ReadableStreamError` uses _reader_.[[closedPromise]]

I don't like (2). There are too many places where we would need branching.

I think the existence of `ReadableStreamReaderGenericInitialize` and `ReadableStreamReaderGenericRelease` already suggest that there should be some concept of a "generic reader". I'm not sure whether this should be expressed in the Web IDL or not. For now, I'm leaning more towards (3).

-- 
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/1050#issuecomment-670076163