Shane F. Carr
Shane F. Carr
How do you envision the nesting? Should it be: 1. `Compact` 2. `Signed`
The 2.0.x component crates I released rely on `icu_provider/alloc` implying `writeable/alloc` and `zerovec/alloc`. If we do this, then we need to patch-release 2.0.x as well as 2.1.x crates, or else...
WG notes: - @sffc The core issue is https://github.com/unicode-org/icu4x/issues/7208 - @robertbastian The cause is that component crates enable `icu_provider/alloc` which they didn't used to do. - @hsivonen Seems like a...
As long as this change doesn't break 2.0.x and 2.1.x crates, I approve the change to the Cargo.toml files. We still must figure out what to do with the serde...
Discuss with: - @sffc - @Manishearth - @younies - @robertbastian
Discussed on 2023-07-04. We will use the auxiliary key model, similar to currency formatter (#1441), which resolves the issues in the OP.
Options: 1. Fine grained data marker attributes 2. Core/Extended Discussion: - @zbraniecki Seems like it would be a footgun if clients aren't loading display names that they need. - @sffc...
Discussion in ECMA-402 meeting: https://github.com/tc39/ecma402/blob/main/meetings/notes-2024-11-25.md#display-names-data-slicing
Trying to organize my thoughts here. There are two different ways we are discussing about reducing data size: 1. Deduplicating identical strings - Example: en-GB and en-US and fr have...
> While I am in favor of allowing clients to fully customize which strings they get, I think removing cold strings is prone to being confusing for people using our...