proposal-cancellation
proposal-cancellation copied to clipboard
Proposal for a Cancellation API for ECMAScript
The last time we looked at this, we were considering a symbol-based protocol in #22. @domenic suggested that we instead consider a host-hook based approach. Part of this will be...
> NOTE: This was originally discussed in #16, however I've created a fresh issue to help discuss this with a fresh perspective. # Introduction As an alternative to adding a...
Implementing `Atomics.waitAsync` based multithreading primitives to Emscripten WebAssembly code libraries, it was realized in https://github.com/WebAssembly/threads/issues/176 that the ability to perform memory deinitialization after having issued a `Atomics.waitAsync` is severely impaired...
I have been working with abort signals and the biggest issue in practically using it was to make sure that all the pieces of code i wrote pass-on the signals...
I noticed that this repo talks a lot about async when it comes to cancellation. I wanted to make sure it also considered synchronous use cases. A good cancellation primitive...
**Edit:** `s/token.try/token.run/g`, clarify that method's return semantics, remove language about an obvious optimization **Edit 2:** Clarify what happens after you run a token, add `token.active` The [zones proposal](https://github.com/domenic/zones) suggested using...
Currently in the current proposal there is no specific course of action that should be taken when cancellation is actually hit. This causes *a lot* of boilerplate to deal with...
This is really a shot in the dark, and I expect some initial resistance, but hear me out on this one. I was thinking you could merge cancelling a request...
This proposal seems significantly more complicated than the cancellation mechanics of generator iterators, so it may be beneficial to align promise cancellation with that of generators. When async generators/iterators are...
Please provide a justification for not using Observable to signal cancellation. The register/unregister mechanism clearly overlaps with the subscribe/unsubscribe methods provided by an Observable and its Subscription. While it's arguable...