• jochen's avatar
    Make sure to use the correct context for eval checks · d008b9ef
    jochen authored
    We can't assume that there's no entered context during microtask
    execution. We also can't assume that we'll never enter an context during
    microtask execution either.
    
    We can however assume that we don't execute microtasks recursively, so
    remembering the length of the entered context stack is enough to decide
    which context to use.
    
    BUG=chromium:635769
    R=verwaest@chromium.org
    
    Review-Url: https://codereview.chromium.org/2350933007
    Cr-Commit-Position: refs/heads/master@{#39627}
    d008b9ef
Name
Last commit
Last update
benchmarks Loading commit data...
build_overrides Loading commit data...
docs Loading commit data...
gni Loading commit data...
gypfiles Loading commit data...
include Loading commit data...
infra Loading commit data...
samples Loading commit data...
src Loading commit data...
test Loading commit data...
testing Loading commit data...
third_party/binutils Loading commit data...
tools Loading commit data...
.clang-format Loading commit data...
.gitignore Loading commit data...
.gn Loading commit data...
.ycm_extra_conf.py Loading commit data...
AUTHORS Loading commit data...
BUILD.gn Loading commit data...
CODE_OF_CONDUCT.md Loading commit data...
ChangeLog Loading commit data...
DEPS Loading commit data...
LICENSE Loading commit data...
LICENSE.fdlibm Loading commit data...
LICENSE.strongtalk Loading commit data...
LICENSE.v8 Loading commit data...
LICENSE.valgrind Loading commit data...
Makefile Loading commit data...
Makefile.android Loading commit data...
OWNERS Loading commit data...
PRESUBMIT.py Loading commit data...
README.md Loading commit data...
WATCHLISTS Loading commit data...
codereview.settings Loading commit data...
snapshot_toolchain.gni Loading commit data...