Robert Bastian

Actually, data "generation" happens in the provider crate, so maybe the driver crate should be `icu_export` (with `ExportDriver`), and the provider crate `icu_provider_datagen` (`icu_datagen` if we don't want to retire...

That's my proposal, just with different names.

We could also move `icu_provider::datagen` into the driver crate.

Latest proposal: * A crate that contains `DatagenDriver`, `icu_provider::datagen::{ExportMarker, ExportableDataProvider, ...}`, the registry (`make_exportable_provider!`), `BakedExporter` * Desired name: `icu_export` * Also would like to rename `DatagenDriver` -> `ExportDriver` * A...

Discussion: * Bikeshed * All provider infrastructure should live in crates prefixed with `icu_provider`, to distinguish them from components ```toml icu_provider_export = { version = "~1.5.0", path = "provider/export" }...

> I would suggest reading through the "Personal life" section of the Wikipedia article and the references therein before deciding whether to name more stuff after Erwin Schrödinger. Thanks for...

I would have also been opposed to the Schrödinger name on the grounds that it's too clever and requires thinking around three corners or knowing what the crate does already....

Previous discussion and background why we want the extra layer: https://github.com/unicode-org/icu4x/issues/2489

`BytesOrStr` sounds like it's an enum and that having bytes is actually fine, when in fact it's an error/gigo case.

Haha I love `ShadyStr`. `SketchyStr` could be another option.