| 04:33 | <Danielle Church> | I suppose my next question is... what now? like, I figure this will bounce around the discourse for a week or two. presumably at some point I fork a repo and try to write something that looks like an actual technical proposal? I'm afraid I'm very new to proposing ideas to a standards committee, any guidance you could give would be greatly appreciated 😅 |
| 05:14 | <Ashley Claymore> | Some info here that might be useful https://github.com/tc39/how-we-work |
| 10:03 | <Danielle Church> | Here's perhaps a weird question. Has anyone written a program that takes the 262 spec as input and produces an interpreting engine as output? |
| 10:19 | <nicolo-ribaudo> | You can check esmeta, which interprets spec+code |
| 10:19 | <nicolo-ribaudo> | But it doesn't generate an interpreter |
| 12:00 | <jmdyck> | Danielle Church: I'm working toward that in https://github.com/jmdyck/ecmaspeak-py |
| 17:04 | <Danielle Church> | oh neat! on both counts, tyvm for the responses 😄 |
| 17:14 | <ljharb> | Danielle Church: i also have implemented many of the spec's abstract operations in https://npmjs.com/es-abstract, so that i can implement my polyfills with as much spec fidelity as possible |