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

> We planned to introduce a generic pipeTo function that interacts with public reader / writer APIs and specific ones implemented natively. What's wrong with the idea?

I mean, the existing (planned) pipeTo can handle arbitrary streams correctly and can handle specific ones (that possibly includes ReadableStream and WritableStream) efficiently. Your proposal seems to drop the former property and I don't see what we get instead.

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