for(of of of);

class X {
  for(x; y=y+1; z) {}
}

I missed the isSafeNumeric discussion due to being asleep at the time. If it gets a continuation, it'd be nice if it was earlier rather than later, but that's of course unlikely (mini-rant: For the last few years 4/6 TC39 meetings have been on North American timezones, with 2/6 on Pacific Time. This is not friendly to remote-participation from Europe. It'd be a little bit friendlier if at least the remote PDT meeting was moved to EDT or even further East).

So posting the comments here that I'd have mentioned out loud had I been there:

• I'm generally positive on enabling a developer to verify that WYSIWYG applies to their numeric string.
• I'm not sure that "safe" is the right word here, though we do already have Number.isSafeInteger. I was thinking that "precise" or "canonical" could be more apt. The attachment point could also be different, as all of the pre-existing Number.is* functions require their input to be a number.
• This seems to correlate very highly with the goals of Decimal, which, if accepted, would also expand the set of strings for which JS can provide a "safe" numerical representation. That proposal is specifically looking to improve the representation of values coming from the real world or elsewhere, which seems like the same domain as this.

I'm on Eastern European Time, and this week's meetings start at 20:00 and end at 03:00 for me. I'm used to having plenty of calls with folks on Pacific Time, but those are all scheduled for the morning there; TC39 calls take up the whole day. Comparatively, a meeting on US Eastern Time ends at my midnight, which is still bad but not as horrible.

I do understand the benefits of running the meetings at different times, and the ones in Europe or Asia are about as much fun for North American participants, but it's the regularity of having all of the virtual meetings on North American timezones and having one of them on Pacific Time that seems a bit extra.

For folk wanting to attend the SeattleJS Community event in-person on Thursday evening, please respond to this poll about the NDA requirement.
❄️

I need to provide the count and names of delegates by midday today in order to stand a chance of getting an exemption.

const myUnit = new Unit({ ...});
const measure = new Measure(1.234, { unit: myUnit });

zxx - non linguistic content, such as onomatopoeia (animal sounds)

This does not reflect what the implementations do, but what the editor thinks to be the least bad thing they ought to do in order to maintain web compatibility.

waldemar:

> const e = new Error(), e2 = new Error();
> Error.captureStackTrace(e);
> Error.captureStackTrace(e2);
> Object.getOwnPropertyDescriptor(e, 'stack').get === Object.getOwnPropertyDescriptor(e2, 'stack').get
> true
> Object.getOwnPropertyDescriptor(e, 'stack').get.x = 1
> 1
> Object.getOwnPropertyDescriptor(e2, 'stack').get.x
> 1

User agents should attach a serialized representation of any interesting accompanying data which are not yet specified, notably the stack property, to serialized.

📣 Announcement

I added a "Stage 2.7 reviewers" column at https://github.com/tc39/proposals?tab=readme-ov-file#stage-2, go there and add reviewers for your proposals or proposals you are a reviewer of

shu For the use counter, I believe after step 16 of https://tc39.es/ecma262/#sec-object.prototype.tostring you'd need to add:

1. If O has a [[ViewedArrayBuffer]] internal slot and _tag_ is not "DataView", trigger the counter.
1. Else, if O has a [[SetData]] internal slot and _tag_ is not "Set", trigger the counter.
1. Else, ... (for all the types listed in that issue)

> const s = new Set()
undefined
> s.add(NaN)
Set(1) { NaN }
> s.add(NaN)
Set(1) { NaN }