Advance to stage 4

[gibson042]

Criteria taken from the TC39 process document minus those from previous stages:

• Test262 acceptance tests have been written for mainline usage scenarios, and merged

https://github.com/tc39/test262/tree/main/test/intl402/Segmenter

• Two compatible implementations which pass the acceptance tests
• Significant in-the-field experience with shipping implementations, such as that provided by two independent VMs

https://github.com/tc39/proposal-intl-segmenter#implementations

Bug tickets to track:

• Chrome/V8: https://bugs.chromium.org/p/v8/issues/detail?id=6891
• Firefox/SpiderMonkey: https://bugzilla.mozilla.org/show_bug.cgi?id=1423593
• Safari/JavaScriptCore: https://bugs.webkit.org/show_bug.cgi?id=213638
• etc.

• A pull request has been sent to https://github.com/tc39/ecma402 with the integrated spec text

tc39/ecma402#553

• All ECMAScript editors have signed off on the pull request

tc39/ecma402#553

[Constellation]

FYI: JSC enabled Intl.Segmenter in Trunk https://trac.webkit.org/changeset/266180/webkit

[vsemozhetbyt]

V8 shipped in https://bugs.chromium.org/p/v8/issues/detail?id=6891#c42

[sffc]

So, can we advance this proposal to Stage 4? Is it too late to get it into ES 2021?

[SphinxKnight]

From what I understand in https://github.com/tc39/notes/blob/master/meetings/2021-10/oct-25.md#conclusionresolution-1 and https://github.com/tc39/proposals/blob/main/ecma402/finished-proposals.md, this is now Stage 4?

I'm really new to this but does this consensus is enough to propose a PR to update https://github.com/tc39/proposal-intl-segmenter/blob/master/README.md and https://github.com/tc39/proposal-intl-segmenter/blob/master/spec.html to Stage 4?

[gibson042]

Yes, but I'm expecting tc39/ecma402#553 to land Segmenter into ECMA-402 proper in the near future so the point will be moot.