| 06:08 | <snek> | cool to see engine262 getting more mind share. i guess that project for evaluating the spec text didn't catch on? |
| 07:15 | <Ashley Claymore> | esmeta? It's run as part of the 262 spec CI https://github.com/tc39/ecma262/blob/main/.github/workflows/esmeta-typecheck.yml |
| 07:16 | <Ashley Claymore> | also ❤️ engine262 |
| 08:04 | <bakkot> | strictly speaking we only run the typechecker part of esmeta, not the actual evaluator |
| 11:23 | <littledan> | Same goes for call syntax, I think(which I previously made the same overlap comment about) |
| 16:09 | <Richard Gibson> | relevant: https://jschoi.org/22/es-dataflow/#five-proposals |
| 16:33 | <Mathieu Hofman> | I have been meaning to fix this for a while. I actually started rewriting the asyncGC helper and the tests, but I really don't have much time to dedicate to this. |
| 16:34 | <Mathieu Hofman> | If someone is interested in taking over I can try to cleanup my old local experiment. Some tests do need to be rewritten to accommodate |
| 19:54 | <jschoi> | Would any delegate be able to sponsor me as an invited expert (https://github.com/tc39/how-we-work/blob/main/invited-expert.md#joining-process) so I can continue championing/co-championing proposals? I’m leaving Indiana University, a TC39 member. |
| 21:44 | <littledan> | Where are you going to, jschoi? |
| 21:57 | <jschoi> | littledan: University of Utah! : ) |