• aperez's avatar
    Use a kMaxSafeInteger instead of Number.MAX_SAFE_INTEGER · 3ece714d
    aperez authored
    Defines and uses a kMaxSafeInteger macro (which expands to the constant
    2^53-1) instead of accessing Number.MAX_SAFE_INTEGER. This saves loading
    the attribute from the Number object, which is slightly faster. This also
    makes it clearer from reading the code that tha value being compared is
    constant.
    
    BUG=
    LOG=N
    
    Review URL: https://codereview.chromium.org/1353953002
    
    Cr-Commit-Position: refs/heads/master@{#30814}
    3ece714d
Name
Last commit
Last update
benchmarks Loading commit data...
build 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...
.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...