Shane F. Carr

I had previously proposed for Extended Year to be Temporal Year, but after we got pushback from ICU for changing a 25-year-stable behavior, Intl Era Month Code decided to define...

I filed an issue against ICU to track whether they want to make Extended Year align with ECMA: https://unicode-org.atlassian.net/browse/ICU-23167 But I don't think we should hold our breath for that...

In order to get this out sooner, I had made a suggestion for a 2.1 release: - 2.1 is: - Full support for the latest Temporal API - Major improvements...

See bikeshed discussion of monotonic_year in https://github.com/unicode-org/icu4x/pull/6800

ICU4X WG discussion: - @robertbastian ICU has landed `extended_year` which I think makes our previous conclusion void, since it said that they weren't going to do it until CLDR 49...

I thought we had discussed at some point having a specialized constructor like `new_root()` that was infallible.

See https://github.com/unicode-org/icu4x/issues/5856 for what we decided to do with Segmenter. I think we could do something very similar for Collator. (going to re-open as I don't think this was addressed...

Or we could close this as a duplicate of #6633

Yeah, it appears that the checks are for invariants between data structs, which shouldn't be reachable with baked data.

`Collator[Borrowed]::try_new` does a data request with the preferences locale, which can always fail.