Jeff Walden

> A workaround to get the time zone resp. era name is to invoke `formatToParts`: That assumes the presentation of the era/time zone in broader context, is suitable for use...

As far as API _surface_ goes -- objects, functions, properties -- SpiderMonkey implements the spec. But https://github.com/tc39/ecma402/issues/113#issue-183908643 is really concerned about conditioning behavior on subtags in a language tag, where...

FWIW https://github.com/tc39/ecma402/pull/429 would probably also resolve this by incidentally enumerating exact validity criteria and linking to both sections 3.2 and 3.3.

The main reason to deterministically order, is to make it impossible for sites to inadvertently depend on implementation-specific behavior. No more and no less. I doubt any existing code depends...

The duplicated-variants restriction and whether it ought apply to `tlang` is rearing its head in SpiderMonkey patchwork and reviewing at this point. Allowing `tlang` to contain duplicate variants, while `unicode_language_id`...

Hmm, okay. That seems pretty clear and direct about invalidity. I can't think of a serious case for not applying that to `tlang` as well -- anything that actually wanted...

We discussed this today and concluded figuring out the duplicate-variant concern does not have to be _immediately_ resolved, and if an ECMA-402 published edition ends up lagging the "living standard"...

My heart is with requiring Type(index) be Number, but I suppose that no-coercion ship sailed twenty years ago. :-( Consistency with DataView et al. seems best to me. Consistency with...

I imagine @erights will have a thing or two to say about this proposal. :-)

> secure code can run in a [frozen realm](https://github.com/tc39/proposal-frozen-realms/) - see [confinement](https://github.com/tc39/proposal-frozen-realms/#confinement-examples) there @benjamingr Okay -- so should I interpret this proposal as intrinsically tied to the success of that...