Ben Lesh

This should be fixed as of [email protected], please update.

CORE TEAM: Needs to be fixed in v7 and v8. We'll likely be introducing new/better/smaller schedulers for v9.

Okay... so here's the thing... THE ORIGINAL ISSUE that was filed here is indeed fixed as of 7.5.7. There's a separate issue that is documented here: https://github.com/ReactiveX/rxjs/issues/6747#issuecomment-1360958245 I'm going to...

I'm so sorry, @backbone87 ... but this PR has a lot going on in it, and it's been so long since I looked at it, that I'm going to close...

After using `AbortSignal` for a large project that was dealing with high-speed emissions, the performance of `AbortSignal`, in particular adding and removing event listeners for `abort` events, was so incredibly...

v8 is going to consolidate on ES2022 and get rid of ES5. That should resolve this issue.

@dancras Apologies on dropping the ball on landing this one. I think there may be another solution here, and we might still try to get this into the 7.x branch.

I've added a commit and moved it over here. I'll try to make sure you get credit for the commits, @dancras https://github.com/ReactiveX/rxjs/pull/7161

@jakovljevic-mladen feel free to merge these into 7.x and master as you please.

> Wouldn't publishing multiple packages for what is essentially the same code actually increase risk of non tree shakable use-case and thus increase bundle size ? It shouldn't... `rxjs` itself...