| 01:59 | <akirose> | leobalter: dyk who is giving the editor's report for Test262 on monday? |
| 02:01 | <leobalter> | I plan to report one specific thing about Test262. I’m not sure if anyone else wants to report more stuff. |
| 02:02 | <leobalter> | Actually, more than one thing about Test262, branch renaming and spec “bugs” |
| 02:22 | <akirose> | It seems like every single scheduling constraint this meeting conflicts with every other scheduling constraiint |
| 02:22 | <akirose> | making this schedule has sucked |
| 02:22 | <akirose> | a ton |
| 02:23 | <rkirsling> | we could try full randomization and keep people on their toes |
| 02:23 | <akirose> | lololol |
| 02:49 | <akirose> | the agenda is way, way, way overfull this meeting |
| 02:53 | <devsnek> | combine items into fights |
| 02:53 | <akirose> | i have been tempted to do so many times. |
| 02:53 | <devsnek> | temporal vs .item() |
| 02:53 | <devsnek> | we could have a bracket |
| 02:53 | <akirose> | wouldn't be a fair fight. |
| 02:54 | <akirose> | i have preferences and i'm in charge of the schedule |
| 02:54 | <akirose> | 😉 |
| 02:54 | <devsnek> | haha |
| 02:54 | <devsnek> | it would be interesting though |
| 02:54 | <devsnek> | if we could only advance one thing each meeting |
| 02:54 | <devsnek> | very slow of course |
| 02:54 | <akirose> | what a dream world |
| 03:21 | <rkirsling> | that would be interesting |
| 03:21 | <rkirsling> | I would say one proposal _per level_ but |
| 05:32 | <Bakkot> | "whichever proposals akirose thinks are most important" is not, like, obviously a worse way to decide how to prioritize things than whatever it is we currently do |
| 05:35 | <Bakkot> | (uh, not to imply that the current mechanism is bad, just that having someone competent decide priorities by fiat is not obviously bad either) |
| 05:46 | <akirose> | 😂🥰 ty Bakkot |
| 05:53 | <rkirsling> | 😂 |
| 11:57 | <littledan> | akirose: Should we have a place on the agenda, like schedule constraints, where we offer our own proposals to be lower priority/on the chopping block? |
| 11:57 | <littledan> | I feel like I've contacted the chair group for this a bunch of times before, and maybe those requests are hard to keep track of |
| 11:58 | <littledan> | this meeting, I'd be OK with operator overloading and extensible numeric literals to be "on the chopping block" |
| 11:58 | <littledan> | I've taken up way more than my fair share of TC39 schedule time in the past... |