TC39 Delegates on 2022-01-19

01:09	<Michael Ficarra>	I've also asked them to post links to resources next to their agenda item once they are prepared
01:14	<Michael Ficarra>	from my invited expert proposal (https://github.com/tc39/Admin-and-Business/issues/187):
01:14	<Michael Ficarra>	Reason for invitation: These researchers from KAIST presented their recently published works to the TC39 editor group. This work includes automatic generation of a reference implementation, automatic generation of a step-through debugger, and tools for helping editors to catch spec errors. We think this work would be useful to share more broadly with the rest of the committee in a plenary.
22:07	<bakkot>	jschoi: your agenda item for Array.fromAsync does not say it's going for stage 3
22:07	<bakkot>	so people might not be reviewing it in enough detail
22:10	<bakkot>	(the rules for advancement eligibility "Proposals looking to advance to stages 2, 3, or 4 must be added (and noted as such)" [emphasis added], so in principle someone can object to advancement on those grounds)
22:15	<bakkot>	also it's currently stage 2; the "stage" column is the stage it is, not going for
22:34	<ljharb>	oops
22:36	<ljharb>	i pushed up a change to that, under the assumption it's meant to be for stage 3. if that's not the intention, we can remove it; if someone missed it between the deadline and now due to the mislabeling, we can deal with that as part of the normal process in plenary
22:36	<Luca Casonato>	also it's currently stage 2; the "stage" column is the stage it is, not going for Oh darn - I think enum and string split might be wrong too. Should both be 0 in that column then, right?
22:37	<ljharb>	yes, i'll fix those too
22:37	<Luca Casonato>	yes, i'll fix those too thx :-)
23:48	<jschoi>	Yeah, my intent was to go for Stage 3. I marked it as such in the pull request but I forgot to add it to the table entry itself. My apologies. 🙇