| 00:07 | <ptomato> | I'll have to audit it for call sites that should change from ? to !, like CreateTemporalDate without passing newTarget (to repeat the example I discussed with bakkot) |
| 00:07 | <ptomato> | likely after that it'll still be a lot of UC |
| 00:08 | <ptomato> | the main decision that's responsible for that is to accept strings or property bags in addition to Temporal objects at API entry points |
| 00:09 | <ptomato> | that's responsible for Get in the case of a non-Temporal object being passed, and ToString in the case of a primitive being passed, which makes coercion operations like ToTemporalDate potentially call UC |
| 00:09 | <ptomato> | nonetheless, I believe it was a good decision |
| 00:25 | <shu> | fair, apologies if it came off like a stronger value judgment than it was intended to be |
| 00:25 | <shu> | i am not the domain expert in the room |
| 00:29 | <ptomato> | no worries, I didn't take it that way |
| 00:29 | <ptomato> | but it did seem like something that warranted an explanation |