Skip to content
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.

Advance to stage 4 #4

Closed
mathiasbynens opened this issue Jun 9, 2016 · 1 comment
Closed

Advance to stage 4 #4

mathiasbynens opened this issue Jun 9, 2016 · 1 comment
Labels

Comments

@mathiasbynens
Copy link
Member

mathiasbynens commented Jun 9, 2016

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

  • Test262 acceptance tests have been written for mainline usage scenarios, and merged
  • Two compatible implementations which pass the acceptance tests

https://github.com/tc39/proposal-regexp-unicode-property-escapes#implementations

Bug tickets to track:

  • Significant in-the-field experience with shipping implementations, such as that provided by two independent VMs

https://github.com/tc39/proposal-regexp-unicode-property-escapes#implementations

tc39/ecma262#1041

  • The ECMAScript editor has signed off on the pull request

@bterlson approved the PR.

leobalter pushed a commit to tc39/test262 that referenced this issue Apr 13, 2017
Proposal: https://github.com/tc39/proposal-regexp-unicode-property-escapes

These tests have been generated by the script at https://github.com/mathiasbynens/unicode-property-escapes-tests. They check all the properties and values that should be supported by implementations against the symbols they’re supposed to match. False positives are detected as well.

Ref. #950.
Ref. tc39/proposal-regexp-unicode-property-escapes#4.
@mathiasbynens
Copy link
Member Author

This proposal advanced to stage 4 at the January 24st TC39 meeting. sheds tear of happiness

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant