mirror of https://github.com/tc39/test262.git
01f73e96ca
See https://github.com/tc39/proposal-temporal/pull/2316 which eliminated an observable call to Array.prototype[Symbol.iterator]() in the case where a calendar's 'fields' property was undefined. The best way I've thought of to test this is to monkeypatch the Array.prototype[Symbol.iterator]() method to make it throw. In some cases, where we are actually expected to iterate the return value from a Temporal.TimeZone's getPossibleInstantsFor() method, we have to provide a custom method for that as well, that returns a non-Array iterable so we don't call the patched Array.prototype[Symbol.iterator](). This normative change reached consensus at the July 2022 TC39 plenary meeting. |
||
|---|---|---|
| .. | ||
| compare | ||
| from | ||
| prototype | ||
| builtin.js | ||
| calendar-case-insensitive.js | ||
| calendar-number.js | ||
| calendar-string.js | ||
| calendar-temporal-object.js | ||
| calendar-undefined.js | ||
| calendar-wrong-type.js | ||
| constructor-full.js | ||
| constructor.js | ||
| datetime-math.js | ||
| hour-undefined.js | ||
| infinity-throws-rangeerror.js | ||
| length.js | ||
| limits.js | ||
| microsecond-undefined.js | ||
| millisecond-undefined.js | ||
| minute-undefined.js | ||
| missing-arguments.js | ||
| name.js | ||
| nanosecond-undefined.js | ||
| negative-infinity-throws-rangeerror.js | ||
| order-of-operations.js | ||
| prop-desc.js | ||
| second-undefined.js | ||
| subclass.js | ||