Shane F. Carr

I wrote one function in https://github.com/unicode-org/icu4x/pull/5202. Unfortunately it can't be infallible because the `UTCOffsetRecord` fields are public, so they could represent an out-of-bounds offset.

Ok, in #5260 I added ixdtf parsing functions for Date, Time, and DateTime. We should also add them to: - CustomTimeZone - CustomZonedDateTime Similar to how the Date and DateTime...

@nekevss I'm assigning this to you based on https://github.com/unicode-org/icu4x/issues/5201#issuecomment-2215575876.

I noticed that we have - `CustomZonedDateTime::try_iso_from_ixdtf_str` - `DateTime::try_iso_from_str` Why does one have `ixdtf` in the name and the other not?

Discussion: - @sffc Can you write `CustomTimeZone::try_from_ixdtf_str("America/Chicago")` ? - @nekevss I don't think so yet. - @sffc Maybe what we want is: - `CustomTimeZone::try_from_iana_str` (need to think about name) which...

@zbraniecki Do you have a wording suggestion?

OK I applied that suggestion. Look good to merge?

I'm going to merge this and @zbraniecki or @robertbastian can open another PR to revise the wording further if they would like to do so.

For the plural selection support, I think the most straightforward option is: 1. `icu_pattern` takes an optional dependency on `zerovec` 2. `icu_pattern` gets a Count enum similar to the ones...

An abstraction in `zerovec` that would be a useful building block would be `VarZeroDefaultVec` with the following behavior: - Has the same byte representation as `VarZeroVec` _or_ removes the first...