Re: [streams] explicity operate on underlying source and sink instead of public methods (#321)

> I'm used to getting this for free through the use of webidl.

Sure, but that's pretty crappy and non-extensible layering, making ReadableStream explicitly aware of WritableByteStream.

---

BTW we're not going to exactly interface with the underlying sink because that means you could do writes out of order. More like, we're going to use abstract operations that take WritableStreams or ReadableStreams as parameters, and use those. Effectively it goes directly to the underlying sink, but also with all the guarantees you would get through a (non-monkey-patched) use of the public API.

See e.g. [EnqueueInReadableStream](https://streams.spec.whatwg.org/#enqueue-in-readable-stream) for an example. I anticipate having a WriteToWritableStream with similar properties.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/321#issuecomment-91051912