| 00:11 | <ljharb> | sorry i should clarify my question :-) for something that's been presented or will be, what's the reason why they shouldn't be? (obviously "any random repo" shouldn't necessarily be) |
| 00:12 | <Michael Ficarra> | no objection to that |
| 00:13 | <Michael Ficarra> | in fact, Ecma would almost certainly prefer that to be the criteria for pulling it in |
| 16:25 | <Rob Palmer> | Reminder: The Helsinki meeting is in 6.5 weeks time! Please use the in-person registration form and then advertise yourself on the Doodle if you intend to attend in-person. I recommend stocking up on Fazer chocolate whilst you are there. |
| 18:24 | <ptomato> | is there standard language for consulting the various tables in the spec? |
| 18:24 | <ptomato> | e.g. as in UnicodeMatchProperty |
| 18:25 | <ptomato> | when you have a value that's listed in a table column, and you want to find the other pieces of data in the same row |
| 18:26 | <ptomato> | if we have standard language for this, it'd be good to document it — currently, esmeta can't make any sense of phrasing like in UnicodeMatchProperty |
| 18:47 | <bakkot> | I don't think there's standard language, no |
| 18:47 | <bakkot> | I did something vaguely similar, but not identical, in https://github.com/tc39/proposal-regex-escaping/pull/77/files |
| 18:48 | <bakkot> | |
| 18:50 | <ptomato> | "of the row whose X column contains Y" — that at least is more explicit than "corresponding row" referring back to some unspecified previous algorithm step |