[regexp] extend \p syntax to binary and enumerated properties.

[regexp] extend \p syntax to binary and enumerated properties.

Also make the syntax a bit less complicated and speculative.

R=littledan@chromium.org
BUG=v8:4743
LOG=N

Committed: https://crrev.com/e39ba01420733cf5fa7a16f9c91dcc8b8b044a47
Cr-Commit-Position: refs/heads/master@{#35344}

[Yang, 2016-04-01 09:51:42]

The CQ bit was checked by yangguo@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-04-01 09:51:53]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1845243002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1845243002/1

[commit-bot: I haz the power, 2016-04-01 10:24:50]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-04-01 10:24:51]

Dry run: This issue passed the CQ dry run.

[Yang, 2016-04-05 09:32:57]

On 2016/04/01 10:24:51, commit-bot: I haz the power wrote:
> Dry run: This issue passed the CQ dry run.

ping

[Dan Ehrenberg, 2016-04-07 22:13:25]

lgtm

Sorry for the delay in review. I like this change, and it's fine to submit this
way as it's not yet staged. Let's make sure to let our colleagues at Microsoft
know about this proposal; I've cc'd them.

https://codereview.chromium.org/1845243002/diff/1/test/mjsunit/harmony/regexp...
File test/mjsunit/harmony/regexp-property-exact-match.js (left):

https://codereview.chromium.org/1845243002/diff/1/test/mjsunit/harmony/regexp...
test/mjsunit/harmony/regexp-property-exact-match.js:14:
assertDoesNotThrow("/\\p{InCyrillic_Supplementary}/u");
For these tests which are changing from assertDoesNotThrow to assertThrows,
would it make sense to put another test in for using the syntax properly, either
here or in the more relevant file (e.g.,
test/mjsunit/harmony/regexp-property-blocks.js for this one)? Or would that be
completely redundant?

[Yang, 2016-04-08 05:16:31]

On 2016/04/07 22:13:25, Dan Ehrenberg wrote:
> lgtm
> 
> Sorry for the delay in review. I like this change, and it's fine to submit
this
> way as it's not yet staged. Let's make sure to let our colleagues at Microsoft
> know about this proposal; I've cc'd them.
> 
>
https://codereview.chromium.org/1845243002/diff/1/test/mjsunit/harmony/regexp...
> File test/mjsunit/harmony/regexp-property-exact-match.js (left):
> 
>
https://codereview.chromium.org/1845243002/diff/1/test/mjsunit/harmony/regexp...
> test/mjsunit/harmony/regexp-property-exact-match.js:14:
> assertDoesNotThrow("/\\p{InCyrillic_Supplementary}/u");
> For these tests which are changing from assertDoesNotThrow to assertThrows,
> would it make sense to put another test in for using the syntax properly,
either
> here or in the more relevant file (e.g.,
> test/mjsunit/harmony/regexp-property-blocks.js for this one)? Or would that be
> completely redundant?

thanks for the review! will add more tests once I'm back from vacation.

[Yang, 2016-04-08 05:16:50]

The CQ bit was checked by yangguo@chromium.org

[commit-bot: I haz the power, 2016-04-08 05:16:53]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1845243002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1845243002/1

[commit-bot: I haz the power, 2016-04-08 05:39:35]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-08 05:39:50]

Description was changed from

==========
[regexp] extend \p syntax to binary and enumerated properties.

Also make the syntax a bit less complicated and speculative.

R=littledan@chromium.org
BUG=v8:4743
LOG=N
==========

to

==========
[regexp] extend \p syntax to binary and enumerated properties.

Also make the syntax a bit less complicated and speculative.

R=littledan@chromium.org
BUG=v8:4743
LOG=N

Committed: https://crrev.com/e39ba01420733cf5fa7a16f9c91dcc8b8b044a47
Cr-Commit-Position: refs/heads/master@{#35344}
==========

[commit-bot: I haz the power, 2016-04-08 05:39:51]

Patchset 1 (id:??) landed as
https://crrev.com/e39ba01420733cf5fa7a16f9c91dcc8b8b044a47
Cr-Commit-Position: refs/heads/master@{#35344}