itoa VS unicode-xid

The hyper package for the crab language actually has a dependency on a package that does itoa (among others) so IMO the problem exist there too and most non trivial packages will be bloated

I see itoa which seems trivial on the surface. The implementation is highly optimized, but it's also covering all the different cases. I'm guessing this is for printing match counts or line numbers, and if this is actually a bottleneck for ripgrep — which seems unlikely — then maybe it's worth it. You know your own needs, and if it was a bottleneck, I bet you could do just as well, if not better, with a custom, smaller, simpler solution inside ripgrep. (i.e. just make sure the power-of-ten denominators are available at compile time so the compiler won't generate divisions.)

Another is unicode-xid. The entire package is literally a constant lookup table. Again, I've embedded Unicode tables in my own programs a number of time. The original tables are machine-readable, and transforming them into code is so simple I usually don't even bother writing a script to do it, just an on-the-fly editor macro.