proposal-async-context
proposal-async-context copied to clipboard
tc39
Async Context for JavaScript
In current proposal `snapshot()` is a static method capturing full context of all `AsyncContext` variables. As a result `snapshot.run()` impacts all `AsyncContext` users. This differs from `asyncVar.run()` usage where current...
I had a call with @andreubotella the other day explaining some of what APM vendors want from context management that we don't have now, explaining the use cases, how we...
This is my first time going through this proposal, and as I was looking at the following example, I couldn't help but feel like I was in _callback hell_ again:...
It's a crazy idea. I'm not sure this discussion belongs to this repo, but this feels related so I'm giving it a try. ## Fact: people patch globals Over the...
_(originally posted by @gibson042 in https://github.com/tc39/proposal-promise-try/issues/15#issuecomment-2045965423)_ > I have reservations about ~~`Promise.try`~~ AsyncContext.{Snapshot,Variable}.prototype.run accepting variadic arguments that leave no room for ever specifying a receiver—setting it apart from Function.prototype.{apply,call} and...
I've been looking at how AsyncContext would integrate with various APIs and events in the web platform. These are my conclusions: # Web APIs These can be grouped in various...
In the spec, the key-value map data structure mapping `AsyncContext.Variable` objects to their values is called the "Async Context Mapping Record". However, the various fields in which it's stored have...
The AsyncContext store is a mapping from `AsyncContext.Variable` objects to arbitrary JS values, which cannot be iterated, and whose entries can't be observed unless you have the `AsyncContext.Variable` key. This...
Opening a placeholder issue on "[Task termination](https://docs.google.com/document/d/1yQy8RNeGXLr99bNpy-7tA1Ch7wN0piekp_-JwxC8FtA/edit#)", which Chrome has brought up as a necessary part of their Task Attribution API. They want to know when a particular task execution...
