- From: Domenic Denicola <notifications@github.com>
- Date: Tue, 10 Feb 2015 09:09:19 -0800
- To: whatwg/streams <streams@noreply.github.com>
Received on Tuesday, 10 February 2015 17:10:02 UTC
> IIRC, I've been thinking that they should just return a promise rejected with a TypeError indicating invalid state error. Sorry if I'm missing something discussed in the past. I'm sure they were but I kind of forget the reasoning too :). It was very early days. I think the idea was that your intent is kind of to shut down the stream and make sure no resources leak. And if you're already closed/errored then you've already accomplished that so you shouldn't get an error. But, I see the perspective of wanting to tell developers they are being overzealous too. I will see if we can get any opinions from Twitter (that hasn't been too successful in the past) and we could also survey other libraries (both for streams and for other disposable resources). But I am OK with making them TypeErrors. --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/266#issuecomment-73739382
Received on Tuesday, 10 February 2015 17:10:02 UTC