• yangguo's avatar
    Disable experimental natives when creating a start-up snapshot. · efe828e6
    yangguo authored
    Re-installing experimental natives after deserialization causes failures if
    said experimental native is already included in the snapshot. However, there
    is no way to tell whether a certain harmony feature has been included.
    
    Experimental natives may also be turned on/off on-demand, which a snapshot
    that includes them would not support for all cases.
    
    The simple solution for the meantime is to never include experimental natives
    in the snapshot and initialize them after deserialization on-demand.
    
    R=vogelheim@chromium.org
    
    Review URL: https://codereview.chromium.org/981473002
    
    Cr-Commit-Position: refs/heads/master@{#26982}
    efe828e6
Name
Last commit
Last update
benchmarks Loading commit data...
build Loading commit data...
include 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...
.ycm_extra_conf.py Loading commit data...
AUTHORS Loading commit data...
BUILD.gn Loading commit data...
ChangeLog Loading commit data...
DEPS Loading commit data...
LICENSE 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...
Makefile.nacl 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...