Richard Gibson

[_TypedArray_](https://tc39.es/ecma262/multipage/indexed-collections.html#sec-typedarray), [%TypedArray%.from](https://tc39.es/ecma262/multipage/indexed-collections.html#sec-%typedarray%.from), and [Array.from](https://tc39.es/ecma262/multipage/indexed-collections.html#sec-array.from) have a lot of redundancy between their iterator vs. array-like consumption branches, but they are also unnecessarily divergent from each other. | API | iterator input...

Normative: Update String toLocale{Lower,Upper}Case to ResolveLocale with best-fit matching

8

Fixes #896 * Do not ignore locales after the first in the list returned by CanonicalizeLocaleList(_locales_) (observable via e.g. `"I".toLocaleLowerCase(["zzz", "tr"]) === "ı"`). * Match against the items of that...

Editorial: Simplify NumberFormat

9

* Collapse rounding mode negation data into one table. * Fold GetUnsignedRoundingMode into ApplyUnsignedRoundingMode

Objects returned from `resolvedOptions()` sometimes omit fields, but generally only when they have no meaningful interpretation (e.g., [NumberFormat](https://tc39.es/ecma402/#sec-intl.numberformat.prototype.resolvedoptions) {minimum,maximum}{Fraction,Significant}Digits or [Collator](https://tc39.es/ecma402/#sec-intl.collator.prototype.resolvedoptions) `numeric`/`caseFirst` when those are not relevant extension keys). But...

Operations specific to DateTimeFormat should have names indicating that

1

_(originally posted by @gibson042 in https://github.com/tc39/ecma402/pull/923#discussion_r1797727493)_ e.g., {Basic,BestFit}Matcher → DateTimeFormat{Basic,BestFit}Matcher

Multipage should be more accessible

5

Having multipage support is great, but it should be more accessible... for example, loading the single-page https://tc39.es/ecma262/ from a linked term in https://tc39.es/ecma402/ or loading a build preview such as...

As suggested at https://x.com/gibson042/status/1958775673797120398 and updated to include named capture groups. Note that this is still not reliable for patterns with flag `v`, which supports nested character classes.

Operation descriptions should appear in JSDoc doc comments

3

**Is your feature request related to a problem? Please describe.** I'm frustrated when my [GraphQL operation](https://spec.graphql.org/September2025/#sec-Language.Operations) descriptions are lost in the translation to TypeScript. **Describe the solution you'd like** I'd...

Represent operation descriptions as JSDoc

1

## Description Represent operation descriptions as JSDoc doc comments. For example, request document ```graphql """ Get summary information about the specified user. """ query user { user(id: 1) { id...