icu4x
icu4x copied to clipboard
Solving i18n for client-side and resource-constrained environments.
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...
See also: #5523, for the holistic design for helper ULE abstractions The original design of ZeroVec and VarZeroVec was for them to be Cow-like types that fully supported mutation. In...
`FlexZeroVec` isn't used, and the VZV mutation code is somewhat nice to have but also is a lot of gnarly unsafe that I'd rather just not maintain or have an...
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...
Related: https://github.com/unicode-org/icu4x/issues/5523 and https://github.com/unicode-org/icu4x/pull/5531 https://github.com/unicode-org/icu4x/pull/1556 It fits into the holistic zerovec design to have a new type `ZeroCow`. It holds onto an owned-or-borrowed VarULE. There is no need to have...
https://github.com/unicode-org/icu4x/issues/5378 is adding `VarZeroLengthlessSlice`. However, it cannot be used inside `VarZeroSlice` because `VarZeroSlice` has an optimization where empty slices are represented as the empty array, so we cannot do ```rust...
Paper: https://arxiv.org/abs/2102.06959 Talk: https://www.youtube.com/watch?v=0s9F4QWAl-E Interesting slide: I think we're using the Reingold/Dershowitz algorithms, so looks like we can do a lot better.