788c96a955
Previously, the Intl implementation tracked types two ways: - In the intl_initialized_marker_symbol - In various named properties of the intl_impl_object_symbol value As far as I can tell, these will never disagree with each other, modulo bugs in Intl itself. This patch removes the second type checking system. This reland includes a fixed type check for Intl.DateTimeFormat.prototype.formatToParts , which is the only Intl method which is not bound. All future methods will follow this pattern. The second reland ensures that a newly inserted test is only run if Intl is present. BUG=v8:5751,chromium:677055, v8:4962 CQ_INCLUDE_TRYBOTS=master.tryserver.v8:v8_linux_noi18n_rel_ng TBR=yangguo@chromium.org Review-Url: https://codereview.chromium.org/2623683002 Cr-Commit-Position: refs/heads/master@{#42152} |
||
---|---|---|
.. | ||
break-iterator | ||
collator | ||
date-format | ||
general | ||
number-format | ||
overrides | ||
string | ||
assert.js | ||
bad-target.js | ||
intl.gyp | ||
intl.isolate | ||
intl.status | ||
not-constructors.js | ||
OWNERS | ||
regexp-assert.js | ||
regexp-prepare.js | ||
regress-4870.js | ||
regress-5179.js | ||
testcfg.py | ||
toStringTag.js | ||
utils.js |