Re: [whatwg/streams] The cloned writable problem (#976)

+1 to all this. I'd love to hear from community members what they think, about both the problem space and proposed solution.

Regarding

> This new operation could in principle be exposed on the ReadableStreamDefaultReader object, but isn't because of its limited utility. Instead, we keep it as an internal abstract operation for now, only used by the pipeTo implementation.

it would also be interesting to hear if folks can think of a use case for exposing this. I am a bit uneasy with making pipeTo depend on functionality that is not also exposed as public APIs, but it's hard to figure out what else would use this, so I agree with the OP that it's better to not expose it for now. Maybe some of the stuff in https://github.com/whatwg/streams/issues/329 or https://github.com/whatwg/streams/issues/324 is related, although this issue focuses on the close signal and not the individual chunk signals.

-- 
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/issues/976#issuecomment-446877014