2026-02-03 [07:20:29.0238] https://front-end.social/@Wilto/116002214854625680 (forwarded from #tc39-ecma402:matrix.org) [12:30:33.0227] mat said he's good; he got ron to review it 2026-02-04 [06:29:20.0141] The deadline for registering for the March Plenary meeting in New York is 24th Feb. So far we have 19 sign-ups! Please register here if you have not done so already. - [**In-person registrations for March TC30 Plenary**](https://github.com/tc39/Reflector/issues/573#issuecomment-3847754536) [06:29:33.0641] * The deadline for registering for the March Plenary meeting in New York is 24th Feb. So far we have 19 sign-ups! Please register here if you have not done so already. - [**In-person registrations for March TC39 Plenary**](https://github.com/tc39/Reflector/issues/573#issuecomment-3847754536) [06:39:41.0318] Is there a list of registrations anywhere? I'm pretty sure I registered a while ago, but not 100% certain [07:23:41.0252] you are registered [07:37:32.0411] There should be a confirmation mail to your filled email inbox, like "Thanks for filling out this form: TC39 March 2026 In-Person Registration" 2026-02-06 [09:49:26.0436] is there a preferred convention for single-line vs multi-line if statements in ecma262? [09:50:06.0779] > 1. If ? SomethingBad(_input_) is **true**, throw a **TypeError** exception. vs > 1. If ? SomethingBad(_input_) is **true**, then > a. Throw a **TypeError** exception. [10:01:14.0158] there's a bunch of guidelines in our editorial conventions: https://github.com/tc39/ecma262/wiki/Editorial-Conventions#algorithm-conventions 2026-02-10 [17:00:13.0641] what does this mean concretely? "if an early-exiting if/else has just two branches (i.e. not an if-else cascade like in some Math functions), and the two branches are substantially similar and short, prefer a single step" [17:00:44.0339] does it mean to prefer > If Something(), return _thing_; else return _other_. [17:01:05.0399] over > 1. If Something(), return _thing_. > 2. Return _other_. ? [17:01:08.0769] * over > 1. If Something(), return _thing_. > 2. Return _other_. ? [17:01:26.0396] * does it mean to prefer > 1. If Something(), return _thing_; else return _other_. [17:02:00.0748] yeah [17:02:11.0764] ok [17:02:14.0585] thanks [17:02:21.0586] but not this? [17:02:37.0674] > 1. If Something(), throw a **TypeError** exception; else return _thing_. [17:02:45.0499] because the two branches aren't substantially similar? [17:03:00.0912] "substantially similar" is always vibes, but personally I would write that as two steps for that reason, yes [17:03:24.0222] all right, got it. thanks [10:07:06.0578] existing preference on > the Foo column of Table 777 vs/ [10:07:27.0174] * existing preference on > the Foo column of Table 777 vs > the "Foo" column of Table 777 [10:07:27.0780] ? [10:09:20.0839] both 402 and 262 use both, but the latter is more prevalent in 262 and vice versa [10:16:29.0695] I only see quoted occurrences in 262 [10:17:21.0637] I'm searching for `column of Table` and see 14 occurrences [10:20:11.0884] in NumericToRawBytes there's "Let _conversionOperation_ be the abstract operation named in the Conversion Operation column in Table 70 for Element Type _type_." [10:31:02.0465] ah, we should fix that to use `column of Table` and quote the column name like the rest [10:43:18.0269] I think I also saw one instance of something like "column one of Table 777" [10:47:03.0469] I'd be very surprised if we referred to a column numerically in 262, but if we did, please open an issue. [10:56:11.0529] found it again, it's in CreateIntrinsics https://tc39.es/ecma262/#sec-createintrinsics [10:59:10.0654] https://github.com/tc39/ecma262/issues/3755 [11:01:12.0981] thanks