- From: isonmad <notifications@github.com>
- Date: Mon, 12 Dec 2016 18:59:41 -0800
- To: whatwg/streams <streams@noreply.github.com>
Received on Tuesday, 13 December 2016 03:00:13 UTC
Like the code currently notes: ```js // TODO: Should we notify the sink of this error? ``` For readable streams, the underlyingSource gets notified because the exception gets rethrown from `controller.enqueue()`, which isn't an option for writable streams. Without a way to know when the stream becomes errored due to the strategy throwing or returning an invalid number, there's no way to know that it should clean up its resources, or to propagate the error forward if the writable stream is just one end of a transform stream. Should `underlyingSink.abort` be overloaded to also be called with a) the exception size() threw, or b) a RangeError if it returned a bad value, and not just when a producer calls `writer.abort()`? That or add an entirely new callback method just for this to either the sink or to the strategy itself. -- 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/628
Received on Tuesday, 13 December 2016 03:00:13 UTC