André Bargull

Temporal: Add coverage for modified Array iteration when called from CalendarFields/GetPossibleInstantsFor

2

It'd be nice to have coverage when the built-in Array iteration has been modified to ensure implementations correctly handle this case in CalendarFields and GetPossibleInstantsFor. CalendarFields: ```js let observed =...

This test case crashes in both V8 and SpiderMonkey (with the patches from applied): ```js let calendar = new class extends Temporal.Calendar { fields(names) { return ["20", ...super.fields(names), "10"]; }...

Editorial: Use named records for DateTimeFormat format records

2

This PR aims to restructure [Intl.DateTimeFormat Constructor - Internal Slots](https://tc39.es/ecma402/#sec-intl.datetimeformat-internal-slots) to use named Record types instead of ad-hoc records. In the process of this clean-up, some editorial bugs were found...

Editorial: Various editorial updates

2

Various editorial updates, including changes to align with ECMA-262 conventions and some editorial bug fixes. --- The PR applies on top of https://github.com/tc39/ecma402/pull/826.

`new Intl.RelativeTimeFormat("en", {numberingSystem:"hanidec"}).format(2, "days")` is currently spec'ed to return the string `"in 2 days"` instead of `"in 二 days"`. `new Intl.RelativeTimeFormat("en-u-nu-hanidec").format(2, "days")` is correctly spec'ed to return `"in 二 days"`,...

Canonicalization for Calendar identifiers?

2

Previously reported at tc39/proposal-temporal#2314, but that issue was closed after the case-normalisation part was fixed. Q: Should `new Temporal.Calendar("islamicc").id` return `"islamicc"` or the canonical identifier `"islamic-civil"`? If no canonicalisation should...

AvailableCurrencies and default fallback for unsupported currencies in NumberFormat

1

: > [...] currencies for which the implementation provides the functionality of Intl.DisplayNames and Intl.NumberFormat objects. But in [PartitionNumberPattern](https://tc39.es/ecma402/#sec-partitionnumberpattern), step 8.k.iii: > [...] If the implementation does not have such...

"this value" and "NewTarget" no longer defined in Built-in Function Objects

1

#3145 removed the descriptions for `this value` and `NewTarget` from [Built-in Function Objects](https://tc39.es/ecma262/#sec-built-in-function-objects), but [ECMAScript Standard Built-in Objects](https://tc39.es/ecma262/#sec-ecmascript-standard-built-in-objects) refers to these descriptions: > In the description of a particular function,...

#2045 made ArrayIterator and RegExpStringIterator no longer reentrant, which doesn't match implementations. The following test case should throw a `TypeError` per the current spec, but does throw `"unreachable"` in all...

The first step in Atomics.{add,sub} calls TypedArrayElementType without actually validating the input is a TypedArray. [Atomics.add \( typedArray, index, value \)](https://tc39.es/ecma262/#sec-atomics.add): > 1. Let type be [TypedArrayElementType](https://tc39.es/ecma262/#sec-typedarrayelementtype)(typedArray). > 2. ...