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

Unless we expect a proliferation of stream types, this does not seem a terrible problem.  I think you would want ReadableByteStreams to understand WritableStream+WritableByteStream, but ReadableStream might only understand WritableStream underlying sink.

It seems this can be done by just looking for the right sink duck types, no?

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