| 22:46 | <littledan> | Shu added a schedule constraint for AsyncContext since he's getting the background on that magical API that Justin found. It's pretty weird, it was implemented in https://chromium-review.googlesource.com/c/v8/v8/+/2005849 but I can't find any usages. |
| 22:47 | <littledan> | It'd be nice to identify where this implementation falls over for thenables, and whether that's something to fix at the V8 level, or whether it's something for each custom thenable to do something-or-other (I don't know exactly what) |
| 22:48 | <James M Snell> | It's also worth pointing out that it should be possible to workaround with thenables by using something like Node.js' AsyncResource. Not elegant but it gets the job done. |
| 22:53 | <littledan> | right, or as it's called in this proposal, wrap |
| 22:54 | <littledan> | so, the question in my mind is: is Justin's example something that V8 should fix, or should it just be fixed by saying, Working As Intended, use wrap if you want it to have the other behavior |
| 22:54 | <littledan> | (this is concretely something we should get back to V8 on) |
| 23:14 | <Justin Ridgewell> | Yoav’s work is also using this API, and I can’t imagine that Task Attribution is happy with the way micro tasks aren’t properly tracked |