-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using aHash 0.5 with wasm #59
Comments
Per the doc here it seems like this occurs because its not clear which interface it should use on The only direct workaround I see is to do what you have outlined above or to depend on either |
Ah, yeah that makes sense. What is aHash using randomness for? Is it to defeat DOS attacks? Can it be made an opt-in? |
I just realized I need my project to compile and work where there is no (easy) source of randomness (inside of wasmtime), so I think I'm forced to revert to aHash version |
Yes, and it is. See https://github.com/tkaitchuck/aHash/blob/master/compare/readme.md#dos-resistance |
No need to do that, just disable the |
If I do that I don't have access to |
This may be orthogonal, but isn't wasmtime |
@tkaitchuck wasi is pretty new and experimental, and I would like my library to also work without it. |
Hi!
I found a small issue when using aHash with
--target wasm32-unknown-unknown
. Starting in aHash version0.5
I get this:There is a simple workaround:
I was wondering if aHash could have some helpful feature flag for this (
features = ["std", "wasm"]
), or maybe even detect the wasm32 target? I'm not great with howCargo.toml
dependencies work :)PS: I really love using aHash as a faster drop-in replacement for
HashMap
andHashSet
.The text was updated successfully, but these errors were encountered: