Perfect hashing with hashify

[xamgore]

So, it turns out there are more than one approach for perfect hashing. Hashify is one of those.

For large tables they promise to be at least 40% more performant, while decreasing the compilation time. I think it worth a try.

---

I am working on this one, as I wanna play with build.rs mechanics. But can't run unescape benchmarks to compare results. There must be some features to be included, which I can't figure out.

[xamgore]

I have tried the crate and considering the noise threshold = 10%, results are good enough:

unescape/unescape_slow/sample_128_normal
                 change:
                        time:   [-5.4879% -5.2733% -5.0280%] (p = 0.00 < 0.01)
                        thrpt:  [+5.2942% +5.5669% +5.8066%]

unescape/unescape_attribute_slow/sample_128_normal
                 change:
                        time:   [-6.6267% -6.4116% -6.2112%] (p = 0.00 < 0.01)
                        thrpt:  [+6.6226% +6.8508% +7.0970%]

unescape/unescape_slow/sample_128_bare
                 change:
                        time:   [-19.504% -19.265% -19.013%] (p = 0.00 < 0.01)
+                       thrpt:  [+23.477% +23.862% +24.230%]

unescape/unescape_attribute_slow/sample_128_bare
                 change:
                        time:   [+8.8047% +9.1306% +9.4847%] (p = 0.00 < 0.01)
                        thrpt:  [-8.6630% -8.3667% -8.0922%]

unescape/unescape_slow/sample_128_none
                 change:
                        time:   [-0.0003% +0.2743% +0.5688%] (p = 0.01 > 0.01)
                        thrpt:  [-0.5656% -0.2736% +0.0003%]

unescape/unescape_attribute_slow/sample_128_none
                 change:
                        time:   [-0.4180% -0.1345% +0.1508%] (p = 0.23 > 0.01)
                        thrpt:  [-0.1506% +0.1347% +0.4198%]

unescape/unescape_slow/sample_128_invalid
                 change:
                        time:   [-25.087% -24.867% -24.620%] (p = 0.00 < 0.01)
+                       thrpt:  [+32.661% +33.097% +33.488%]

unescape/unescape_attribute_slow/sample_128_invalid
                 change:
                        time:   [+6.0339% +6.3088% +6.5929%] (p = 0.00 < 0.01)
                        thrpt:  [-6.1851% -5.9344% -5.6905%]

On M3 MAX, matchgen is 2-4x faster. Don't know how and why 😄

[xamgore]

Ok, there is also quickphf.