[parser] Don't block PRIVATE_NAME in ParseObjectPropertyDefinition
This is already blocked when PRIVATE_NAME is parsed anyway, and we simply need to make sure that we don't continue. So marking the prop_info->kind as kNotSet will do what you want via the unexpected path rather than through the main hot path. Bug: v8:8808 Change-Id: I93beb80a89cf764cd79d6c3ec3a5fc763a98c4d6 Reviewed-on: https://chromium-review.googlesource.com/c/1472635Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#59600}
Showing
Please
register
or
sign in
to comment