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

Interesting!

Moving to an `interface mixin` is indeed editorial. I can see the appeal. I've also run into the desire to link to a single public API for things like https://whatpr.org/streams/1050.html#dom-underlyingsource-cancel; as you can see I currently use text like "`defaultReader.cancel()` or `byobReader.cancel()`".

However, I think we should game this out a bit more. If we start using mixins for something like this... will we also want to use them for controllers? A lot of internal slots _and_ public APIs are shared between the two readable stream controllers. And heck, maybe more abstract ops would be shared, if we had a common place to share them. (Not sure about that one.)

I also worry a bit about the impact on spec readability of splitting readers out so that you have to read at least 2 sections per reader, instead of 1. This is most stark for the domintro sections, aimed at web developers; would we split those up?

I'll proceed to respond to your questions and do a review based on sticking with (3), but I'm more open to discussing interface mixins 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/pull/1050#issuecomment-670696321