Shane F. Carr

- @robertbastian worried if we don't put in the enum, every caller of PluralElements you will forget to check for the specific cases (if you only handle general cases). -...

Nested writeables can usually be composed in such a way that it should be equivalent to a loop when unrolled, but I agree it can be tricky to get to...

Closing this because all work is tracked elsewhere

I like `zeropattern` and `icu::preferences` or maybe `icu::prefs`

Additional notes from 2024-07-18: Options for `icu_preferences` crate structure? - `icu_preferences` re-exported as `icu::preferences` - `icu_locale_core::preferences` re-exported as `icu::locale::preferences` - `icu_locale_preferences` re-exported as `icu::locale::preferences` Options for `preferences` naming? - `preferences`...

Additional thought from https://github.com/unicode-org/icu4x/pull/5260#discussion_r1684978963: There are sort-of three classes of crates we keep hitting up against: 1. Things that are truly components (internationalization value proposition) 2. Things that are truly...

I still don't think that our Pattern type is sufficiently coupled with CLDR/LDML that it should go into the crate name, unless we establish a common prefix like `cldr_` or...

On preferences: I added `types` and `typed` to the ballot since the things we're exporting aren't actually preferences, they are just the typed enums/structs that preferences include.

Ballot is open: https://docs.google.com/document/d/1Ol0aKsT252WKRavjb38iYZoh8rrFTw6mvKgf-5HB-Gs/edit

I lean toward putting the preferences stuff into `icu_locale_core` simply because it's _fairly_ closely related and I want us to stop adding more crates without any restraint, especially lower-level crates.