Errors thrown in nextHandler passed to subscribe should not tear down observable

[benlesh]

This is coming from the TC39 proposal (cc @jhusain)

Basically, to match the behavior of EventTarget, an error in the handler shouldn't cause the source to stop emitting values. In other words:

Observable.interval(1000)
  .subscribe({
    next(x) {
      if (x === 1) throw new Error('bad');
      console.log(x);
    }
  });

// 0
// ERROR: bad [callstack vomit here]
// 1
// 2
// 3
// ...

[mattpodwysocki]

@Blesh as far as I remember, it stops emitting, but doesn't tear down the Observable, so not quite what you have there. @jhusain am I correct here?

[jhusain]

Keeps emitting, doesn't tear down Observable. The forEach method however continues to work the way subscribe works today.

…

On Thu, Dec 1, 2016 at 7:58 PM, Matthew Podwysocki ***@***.*** > wrote: @Blesh <https://github.com/blesh> as far as I remember, it stops emitting, but doesn't tear down the Observable, so not quite what you have there. @jhusain <https://github.com/jhusain> am I correct here? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2167 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAcfr_U6HXExbNmlw_FMSOZv9WbWGDcnks5rD5dfgaJpZM4LCATi> .

[benlesh]

I think we're going to have to target this for v7. It's an important change, but it will incur a lot of breakage in the community I think.