Daniel Vogelheim ae1e87596d [parser] Introduce 'contextual keyword tokens'. ... Introduce 'contextual keyword' tokens, which are parsed as identifiers but in some contexts are treated by the parser like proper keywords. These are usually keywords introduced by recent ECMAScript versions, which for reasons of backwards compatibility are still permissible as regular identifiers in most contexts. Current usage is to check for Token::IDENTIFIER and then do a string compare. With this change the initial scan will scan them as usual, but will then record the token as IDENTIFIER plus a secondary token with the 'contextual' value. BUG=v8:6902 Change-Id: I6ae390382998cf756a23720bd481cb9c0eb78a72 Reviewed-on: https://chromium-review.googlesource.com/459479 Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org> Reviewed-by: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/master@{#44189}		2017-03-28 12:43:23 +00:00
..
test-parse-decision.cc	include fixing: api.h shouldn't include objects-inl.h	2017-01-09 13:43:28 +00:00
test-preparser.cc	Make isolate explicit param of parsing:: functions	2017-03-28 08:20:56 +00:00
test-scanner-streams.cc	Remove Factory::NewStringFromASCII method.	2017-03-17 17:52:50 +00:00
test-scanner.cc	[parser] Introduce 'contextual keyword tokens'.	2017-03-28 12:43:23 +00:00