Because I couldn't easily control the vendored generator

It's not vendored; feel free to change it

When I ran cargo run --release -- --phf, it generated different generated_phf to current one.
I am not confident to add a new database not breaking it.

Ah yeah, it's not deterministic

Why is it an issue, though? You could make it generate to src/generated_alias.rs and not commit the change to src/generated.rs.

Though it probably makes sense to replace the built-in perfect-hash with the phf crate altogether in a different PR. (We just need to check it doesn't come with size of perf drawbacks).

I didn't know it is not deterministic. I found db bugs here, so I will rewrite db part soon.

ok, bug is fixed but still phf is not ported.

rebase on master but still using phf crate

@youknowone Looks like we're all done here. Am I forgetting anything?

The feature is done.
You may want to rewrite this patch using the internal phf implementation instead of phf crate