Crystal Durham

The optimal solution per my understanding of the proc macro ecosystem is to go back in time and make all tracing dependencies on tracing-attributes an `=` exact version dependency, and...

FWIW, if your used version of `tracing` has an `=` dependency constraint on `tracing-attributes`, it's impossible to pull in an incorrect version of `tracing-attributes` (currently) due to cargo's one-per-major-version rule....

> This means that if users depend on `tracing-attributes` explicitly, and they update just the `tracing-attributes` version, without also updating `tracing`, their code will no longer compile. FWIW it's worse...

I ran into this error on updating rustc and also had it fixed by running `cargo update` to use the latest version of stdweb. EDIT: specifically, I also updated `cargo-web`...

I don't think internal/adjacent tagging would see any use; it's not really useful to have such structure for a unit variant, imho. But maybe I'm wrong; if the implementation effort...

Yeah, for the time being, ICU4x is the way to go. At least until @behnam is active again, this project is effectively on hiatus. If you ping me, I think...

Boring, touches-every-table, would-work-now solution: - New crate, `unic-pua-override` - All crates have an optional feature/dependency on `unic-pua-override` - This is extended to any UNIC dependencies of a UNIC crate -...

That doesn't have to cause breakage. Sketch: ## unic-pua-override ```text override_names = LazyStatic RwLock Map Map::new put_name_override char name = do override_override[char]

We should also mention the expected sister modules `abbr_names`/`long_names`.

Surprisingly, the rsv generation is rather quick _in release mode_. Computers are fast, even with the simple > efficient mindset of the generation code's ownership model. However, we want to...