Tom Kaitchuck

This feature is now available in [v0.8.0](https://github.com/tkaitchuck/aHash/releases/tag/v0.8.0)

the build.rs can easily detect a fuzzing flag. (As can the code.) What do you want the behavior to be when fuzzing? (I don't understand the motivation enough to infer...

Ok. So even counters should be disabled. Because while it would be identical if the process is re-run, if the same code is called twice in a row in a...

Yes, `#[cfg(fuzzing)]` is definitely better than a feature flag, because it can't creep in accidently. IE: Some random dependency specifies it, therefor it gets set on the whole binary accidently....

I have sortof a prototype of this. (Though annoyingly it does not work on ARM) The basic idea is that we could have a feature/flag to check which disables runtime...

This is now available in [v0.8.0](https://github.com/tkaitchuck/aHash/releases/tag/v0.8.0)

It may be better to have a separate HasherBuilder so that it can be changed on a map by map basis.

This may serve as a starting point https://github.com/tkaitchuck/aHash/wiki/How-aHash-is-resists-DOS-attacks

It's kindof odd to have a mode where the upper half of the bits of the hash are all zeros. Given that it is not something that is guaranteed in...

I am not able to reproduce this issue. Can you post the error you are seeing?