Shane F. Carr

Additional discussion on 2022-07-07: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-07-07.md#intlsegmenter-with-urls-email-addresses-and-acronyms

Another option, which I mentioned in the meeting: Keep `GetOption` defined as it is now, and move it to 262. In 262, make new abstract operations as follows: ```html NormalizeOptionsObject...

If we don't want the legacy mode in 262, we could do: ```html NormalizeOptionsObject ( _options_ ) The abstract operation NormalizeOptionsObject massages _options_ into an Object to be subsequently passed...

2021-02-11 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2021-02-11.md#require-options-to-be-an-object-480 We agreed to adopt the new stricter GetOptions behavior in newer APIs, but not to change older APIs to avoid breaking the web with what would most...

> Is it not worth some telemetry to figure out if it would break the web? I'd be happy if someone can volunteer to do this, but from a prioritization...

I filed https://github.com/tc39/ecma402/issues/537 to track updating new ES 2021 proposals.

Given that #538 and https://github.com/tc39/proposal-intl-segmenter/pull/135 are merged, is there anything remaining to do on this issue?

Related: https://github.com/tc39/ecma402/issues/503, https://github.com/tc39/ecma402/issues/470 Thank you for the request. I anticipate that there will be a future iteration to add more measurement units, and every signal for which units are important...

I'm told that the web reality in V8 is that this is a cross-realm symbol, so making it per-realm would require a change in V8. Should we revisit this and...

Got it; according to the OP, the web reality is inconsistent, so someone needs to change. Let's stick with the TC39 conclusion of per-realm.