• adamk's avatar
    Stop treating scopes containing template strings tagged with 'eval' specially · f5828cb4
    adamk authored
    There's no need to mark these as possibly-direct-eval, since all such an
    eval-tagged string will ever get passed is the array of string parts, which
    will be immediately returns (since it's not a string). It will
    never do a lookup in the current scope, nor (in sloppy mode) introduce
    new declarations.
    
    This patch is not intended to change behavior, but I've added tests that
    demonstrate the stuff explained in the preceding paragraph.
    
    Review URL: https://codereview.chromium.org/1580463003
    
    Cr-Commit-Position: refs/heads/master@{#33245}
    f5828cb4
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest 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...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
simdjs Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
webkit Loading commit data...
bot_default.gyp Loading commit data...
bot_default.isolate Loading commit data...
default.gyp Loading commit data...
default.isolate Loading commit data...
ignition.gyp Loading commit data...
ignition.isolate Loading commit data...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...