Justin Grant

My understanding is that sorucemaps are only generated by default in DEV builds. In PROD builds, there should be no sourcemaps emitted by default. Are you seeing different behavior?

> > * Legacy POSIX identifiers that refer to a single fixed UTC offset, such as "EST" or "WET", must be non-primary time zone identifiers that resolve to the corresponding...

TG2 meeting 2023-10-12: Option C above is preferred, with the caveat that we should make the spec text be a recommendation not a normative requirement. I'll prepare a PR. For...

Yep, sorry I haven't done this yet, but will try to get to it in the next few months.

> @justingrant The conclusion from the October meeting was that you would "draft a PR with a recommendation based on Option C that we can discuss further." PR available! #877...

> I think we should go ahead and make a PR. AFAIK, no PR for the ECMA 402 spec is needed. But JSC and V8 don't currently follow the current...

On the other hand, if we want to reify the no-Etc behavior of V8/JSC into the spec, that would require a normative PR. Should we discuss this at the next...

> Is this what the spec currently requires? Yes. There is no filtering out of `Etc/*` and `UTC` in the [spec](https://tc39.es/ecma402/#sec-availableprimarytimezoneidentifiers). All primary time zone identifiers are supposed to be...

> Chromium: https://issues.chromium.org/issues/419464498 Already reported ~~last year~~ in 2021 for Chromium: https://issues.chromium.org/issues/40746018. Currently assigned to @FrankYFTang.

> * Do you have insight into why the authors of the snippets above did not instead use temporary variables that they could have plugged into Object.entries? (Some developers “love...