Shane F. Carr

I transferred the issue to the ECMA-402 repository. I think we should at least add a test for the behavior, if not clarify the spec.

TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-10-06.md#normative-add-new-numbering-systems-kawi-and-nagm-714 Conclusion: Like last year, wait until ICU 72 is fully released before merging this.

Additional TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-11-03.md#normative-add-new-numbering-systems-kawi-and-nagm-714 I also filed #727 to arrive at a longer term process for making these types of updates.

I agree that it makes sense for all Intl objects to support exactly the same set of identifiers that come out of Intl Enumeration. We have a section toward the...

We should resolve this once Intl Enumeration API lands.

TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-10-06.md#normative-update-spec-to-align-with-mdn--preparation-for-temporal CC @FrankYFTang who voiced concerns.

TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-11-03.md#normative-update-spec-to-align-with-mdn--preparation-for-temporal-715

TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-10-06.md#normative-read-date-time-options-only-once-when-creating-datetimeformat-objects Conclusion: Review the Test262 impact. Further discussion is not necessary in this group unless red flags show up. Approved with that condition.

TG2 consensus: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-09-01.md#normative-add-microsecond-and-nanosecond-to-issanctionedsingleunitidentifier-708

+1 on the name `get_or_insert_default` I wanted to use this today, but it's still experimental. :laughing: