Stephen Belanger

> Furthermore, as @littledan points out above, in cases where the only originating context would be the one in which basic tracking systems are set up at page load, that...

I think static snapshot is _fine_, we just need per-instance escape routes. I think we _should_ have a recommended default path which is usable in most cases, we just would...

I actually had a solution to this a _whole bunch_ of years ago which I made when much earlier iterations of context management were being proposed but I think I...

Yes, basically the same idea. In my original implementation I solved the case of repeatable tasks by just adding one extra increment to represent the handle for the task which...

The use case is being able to alter the graph shape for your _own_ representation without altering it for _everyone_. A good example is when tracing the fs module. If...

Snapshot is a container for the value of _all_ stores though, so wouldn't that capture and restore the value of _all_ stores? The purpose of this issue is to request...

It's a small amount of code on top of what is already there, but it's also I think a common enough need that making the DX of this common case...

Why is specific propagation for these methods needed? Would the callbacks not just run in whatever context the methods are called in, since it's synchronous?

Iterators aren't async on their own though, they're just an abstraction over _something else_ that is async. Even an async iterator is just an abstraction over a bunch of promises,...

The particular example I was thinking of was [co](https://www.npmjs.com/package/co), which basically did async/await before async/await existed. I'm not referring to that library specifically though but rather the pattern it presents....