02:59 | <Chengzhong Wu> | the way the spec is written right now, |
11:02 | <Andreu Botella> | Do we want values in the async context mapping to be ECMAScript language values? |
11:03 | <Andreu Botella> | I was thinking that maybe Yoav Weiss's work on task attribution handling could be defined in terms of storing an HTML spec-level value on the mapping for a symbol that's not associated to any AsyncContext instance |
11:04 | <Andreu Botella> | AsyncContext.prototype.get could then assert that the gotten value is an ECMAScript language value |
12:26 | <littledan> | yes, I think this would be a good direction for part of the refactoring patch which also exposes abstract operations for get, run, and the AsyncContext constructor. |