These two crates currently live in utils and are not reexported in the meta crate, yet they use the icu_ prefix.
icu_pattern does not seem ICU-specific, it's just an encoding model for a pattern string. Maybe a name like zeropattern, which is in line with our other data representation crates zerovec and zerotrie, and calls out the zero-copy nature of the implementation, would be more appropriate.
Regarding icu_preferences, I think it should actually be a component, or live in the icu_locale component. If icu_locale is a component, this seems appropriate as a component as well.
These two crates currently live in utils and are not reexported in the meta crate, yet they use the
icu_
prefix.icu_pattern
does not seem ICU-specific, it's just an encoding model for a pattern string. Maybe a name likezeropattern
, which is in line with our other data representation crateszerovec
andzerotrie
, and calls out the zero-copy nature of the implementation, would be more appropriate.Regarding
icu_preferences
, I think it should actually be a component, or live in theicu_locale
component. Ificu_locale
is a component, this seems appropriate as a component as well.