Andreu Botella

While working on the spec text for this, I noticed there are various spec-created iterators which use the generators machinery under the hood through [`CreateIteratorFromClosure`](https://tc39.es/ecma262/#sec-createiteratorfromclosure), and would therefore propagate the...

For sync iterators, it would need a flag on the generator so it doesn't switch to the snapshot active when the execution was last suspended. For async iterators, I don't...

> Because of promises flowing context through the resolve path, if this were to be rewritten with `promise.then(...)` nesting instead of async/await this would behave as expected, which leads me...

> But this is essentially the same as mutating a context in a child call and expecting it to be present in the parent execution: > > ```js > const...

Do APMs need to be able to access the contexts for all of the promises resolved with `Promise.all`? If so, would this be special-cased to `Promise.all`, or are there userland...

One question I have is, if this is such a problem for the tracing use case, why wasn't it caught earlier? The behavior across async continuations in the proposed spec...

@Qard You mentioned (in private communication, I think) that you have been looking at context propagation across multiple languages. So is there any language or framework that has something like...

I've been looking at this again, and this seems like an unlikely change to be accepted, since despite the arguments I made, there's no knowing what would break. Depending on...

I thought the array store in question in the above sample was in the console code, but it seems to happen when dealing with the `load` event: ```js Object.defineProperty(Array.prototype, "0",...