2023-12-19 [18:42:43.0953] Hey, can anyone tell me if the proto-proposal I put on the Discourse (https://es.discourse.group/t/proposal-access-to-constructor-parameters-in-field-initializers/1862) is a reasonable thing to have posted? [09:23:19.0776] > <@dmchurch:matrix.org> Hey, can anyone tell me if the proto-proposal I put on the Discourse (https://es.discourse.group/t/proposal-access-to-constructor-parameters-in-field-initializers/1862) is a reasonable thing to have posted? it's definitely a reasonable thing to have posted, and that's the right place to post it :-) [09:24:18.0916] > <@ljharb:matrix.org> it's definitely a reasonable thing to have posted, and that's the right place to post it :-) Thank you! I always have an anxiety about walking into a place and saying the wrong thing, so I really appreciate the reassurance! 2023-12-20 [20:33:41.0014] 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 😅 [21:14:01.0311] Some info here that might be useful https://github.com/tc39/how-we-work [02:03:49.0715] 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? [02:19:49.0216] You can check esmeta, which interprets spec+code [02:19:57.0703] But it doesn't generate an interpreter [04:00:47.0724] Danielle Church: I'm working toward that in https://github.com/jmdyck/ecmaspeak-py [09:04:37.0481] oh neat! on both counts, tyvm for the responses 😄 [09:14:31.0503] 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