Description[strong] Implement static restrictions on binding 'undefined' in arrow functions
Implements the strong mode proposal's static restrictions on the use of the
identifier 'undefined', for arrow functions. Assumes these restrictions are
intended to be identical to the restrictions on the use of 'eval and 'arguments'
in strict mode. In addition, Location variables inconsistantly named (e.g.
dupe_error_loc vs dupe_loc) are now consistently named the shorter way.
Baseline: https://codereview.chromium.org/1070633002
BUG=v8:3956
LOG=N
Committed: https://crrev.com/3d5717a71bdc19c584c277edce9f75a06e95895f
Cr-Commit-Position: refs/heads/master@{#27756}
Patch Set 1 #Patch Set 2 : fix a merge mistake and formatting #
Total comments: 1
Patch Set 3 : Add tests/fix some existing test flags. #
Total comments: 14
Patch Set 4 : Forgot harmony-sloppy flag in undefined-arrow.js #Patch Set 5 : cr feedback #
Total comments: 2
Patch Set 6 : linebreak #
Messages
Total messages: 20 (11 generated)
|