Benjamin Gruenbaum

> Hello, I would like to use Bluebird instead of native Promises because native stack traces give me no clue where to look for errors that are happening We fixed...

> I think the no-floating-promises rule is problematic and sincerely limit the capability of frameworks. I think it needs more nuance to be generally useful. When writing scripts and tests...

> From my experience turning it on in large codebases - this is not correct. Cases of infallible promises / promises that are optionally awaitable are the exception and from...

@benlesh is someone I trust in both RxJS and AbortSignal and has provided API feedback before. In my opinion @ronag is in the right here and the API _should_ take...

> Why do you think that is the correct way? Why do you think promise API's should support the AbortSignal? That's a good question. This is related to discussions (e.g....

piing

Hey, copying my reply from the duplicate (thanks for finding this Domenic): > wanderview: I'm somewhat ambivalent, but any such API probably also needs something equivalent to clearTimeout(). Maybe using...

@Fishrock123 you and @domenic are not actually disagreeing on this from what I understand. You can have `setInterval` as an async iterator and at the same time have a cancellable...

Thanks for opening, Using `AbortSignal.any([signal])` just to use the fact it exposes an underlying different mechanism in the DOM seems like not a great design. It's similar to making a...

There is a real issue, userland uses `addEventListener("abort"` for resource cleanup and other listeners being able to prevent that is unfortunate. At the moment AbortSignal _already_ has a second dispatch...