Re: [streams] How generic is pipeTo? (#407)

This section of the spec is kind of a mess, I'm sorry.

The intention, per previous discussions in #97, is to have pipeTo actually not be generic. It will only accept true WritableStream objects, and will operate using abstract operations instead of going through the public API. The reference implementation does not yet reflect this.

There's a long dependency chain here unfortunately, such that the proper order is:

- Update writable streams a significant amount, in particular #318 and #319. See also the warning at https://streams.spec.whatwg.org/#ws.
- Then, update pipeTo to work with the new writable stream abstract operations that this will create, and to be non-generic.
- Finally, actually spec pipeTo, instead of having a note saying "please go see the reference implementation for our current best guess."

I'm sorry this isn't ready yet. In general writable streams need more attention. I hope this helps in the meantime, but let me know if perhaps adding a note like this in the spec text would be helpful...

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