Robert Bastian

`icu_testdata` would depend on a less specific version of `icu[_*]`, like `1`.

Does cargo recognise that `1.1.0-cldr62` is later than `1.1.0-cldr61`? Otherwise we could use the third fragment (`1.1.62`), assuming we're not going to change any data struct layouts in minor releases.

Alternatively there's this crate as well https://github.com/Enselic/cargo-public-api

Hmm I remember seeing that `has_escaping_bound_vars` regularly a while ago. Is your toolchain up to date? Can you try running with nightly?

Something else I noticed: `AnyCalendar`, `DateFormatter`, `DateTimeFormatter`, and `ZonedDateTimeFormatter` are the only types in all components that do not use the macro to declare `_with_any_provider` and `_with_buffer_provider`, and have separate...

I agree with Zibi, we already have `extensions::Other` which is the wrapper, `OtherSubtags` shouldn't be on the same level as that's not how `Unicode` and `Transform` work.

`with_provider_unstable` `with_data_provider_unstable`

If we want to go further than the `ShortVec` regression we could put the `Extensions` struct on the heap and cut the size of `Locale` by 75% (216 to 56...

Edited, had a typo that messed up results before. I didn't sleep much. I just tried this with today's nightly: ```rust enum ShortVec { Empty, Single(T), Multi(Vec), } assert_eq!(size_of::(), 32);...

Don't celebrate, this seems very brittle and won't work with `TinyAsciiStr`: https://play.rust-lang.org/?version=nightly&mode=release&edition=2021&gist=89c6184a24634bf80c245ffbcbfc0928