Shane F. Carr

TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2023-10-12.md#should-ecma-402-spec-text-for-time-zone-canonicalization-refer-to-cldr-or-to-iana-as-authoritative-825

@justingrant The conclusion from the October meeting was that you would "draft a PR with a recommendation based on Option C that we can discuss further."

TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2023-05-04.md#intlsupportedvaluesoftimezone-for-utc-etcgmt-and-other-non-contintentnon-ocean-time-zone-identifiers-778

In the latest TZDB, thanks to @justingrant, the legacy zones like "WET" are now links in `backward`. I think that should make this issue easier to resolve, now? `Etc/*` zones...

I think impls should return Etc/* time zones in supportedValuesOf, and not WET/CST/... Is this what the spec currently requires? If so, then maybe we only need to add some...

TG2 discussion: https://github.com/tc39/ecma402/blob/main/meetings/notes-2024-08-22.md#inline-getoperands-into-pluralruleselect

Losing the caller location when bubbling up errors is I think a known issue with the Rust error propagation model, not specific to DataError. CC @yaahc, thoughts on the recommended...

See https://github.com/unicode-org/icu4x/pull/6414 for a possible approach.

For now, I'm just going to wrap a flat `ZeroVec

How does `Cow