Shane F. Carr

#5584

Currently the neo datetime datagen uses the v1 data structs in order to generate v2 data structs. This was a shortest-path solution at the time to get neo up and...

Add datetime API for loading length patterns, sitting on top of semantic skeleta

5

CLDR issue: https://unicode-org.atlassian.net/browse/CLDR-17775 Semantic skeleta allow a lot of flexibility for locales to select the fields most relevant for their formatting. However, they produce different output than date length patterns...

_This issue is intended to be discussed in the context of zerovec 1.0 / holistic design_ I've thought this for a while but I wasn't able to find an issue...

Make derive(ULE) check for public fields

12

Consider the following struct, which exists in ICU4X: ```rust pub struct Region(TinyAsciiStr); ``` To make this into a ULE, it is tempting to simply apply `#[derive(ULE)]`. However, this is unsafe,...

Make property name lookup `get_loose` more efficient and limit recursion depth

1

Address some of the follow-ups in https://github.com/unicode-org/icu4x/pull/5576. CC @robertbastian

We have a fair bit of infra to support it, but I'm not sure if it is still used in the neo datetime code.

Currently they have different representations due to how they order strings. However, this is trivial to fix at runtime by writing a custom comparator in the binary search. Making them...

Someone needs to re-create the `icu4x` crate and publish it with the new description agreed upon in https://github.com/unicode-org/icu4x/pull/5215#issuecomment-2291893070: > For ICU4X, see the `icu` crate.

From @j-luo93 in https://github.com/unicode-org/icu4x/pull/4900: > Sorry for the long-delayed reply. I don't think there's anything from my use case that would guarantee a lookahead > In light of this, do...