• Toon Verwaest's avatar
    [parser] Fix escaped contextual keyword handling · a94c91ca
    Toon Verwaest authored
    Escaped contextual keywords are simply valid identifiers if they do not occur
    in the context where they are a keyword. Escape sequences of the form \uNNNN
    or \u{NNNNNN} must be consumed as part of the identifier.
    
    If such escaped contextual keywords do occur in a context where they are a
    keyword, they are a syntax error. In that case we manually check locally
    whether they are escaped.
    
    Bug: v8:6543, v8:6541
    
    Change-Id: I7e1557963883e722310b9078d7d7636ec94aa603
    Reviewed-on: https://chromium-review.googlesource.com/c/1473293Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
    Commit-Queue: Toon Verwaest <verwaest@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#59628}
    a94c91ca
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
fuzzer Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mkgrokdump Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
test262 Loading commit data...
torque Loading commit data...
unittests Loading commit data...
wasm-js Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
OWNERS Loading commit data...