• Adam Klein's avatar
    [scopes] Clarify and narrow when scopes care about an eval() call · 1c9de0b2
    Adam Klein authored
    There are two reasons for Scopes to need information about eval calls
    inside them:
    
      - Eval in a scope, or any of its inner scopes, turns off a bunch of
        scope analysis optimizations (e.g., all variables have to be treated
        as "used" and context-allocated).
      - Eval in a sloppy declaration scope means allows runtime addition
        of var declarations.
    
    This patch aims to make the code better-reflect this reality.
    It's meant as a pure cleanup, with no expected change in behavior.
    
    Change-Id: I744c5051bb7a90b11420930e9596e5d6c35eb440
    Reviewed-on: https://chromium-review.googlesource.com/602848
    Commit-Queue: Adam Klein <adamk@chromium.org>
    Reviewed-by: 's avatarMarja Hölttä <marja@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#47257}
    1c9de0b2
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...
promises-aplus Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn 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...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...