-
Notifications
You must be signed in to change notification settings - Fork 182
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
Comment on WASM targets where getrandom should never work #152
Comments
I donno much about the range of wasm targets that exist, or what normally happens, but wasm was meant to be quite deterministic, and ours bans any form of real randomness or secrets. I'd assume that no_std wasm has basically nothing unless you'd some additional host interface that supplies it, but not really sure. |
This will get clarified w/ the
Comment either here or in the doc bug if the above seems unclear or incorrect. |
I believe the rust target is wasm32-unknown-unknown. If I read lib.rs correctly, wasm32-unknown-unknown without wasm32_bindgen or wasm32_stdweb compiles to dummy.rs, which always errors. This is correct behavior for "perfectly" deterministic wasm targets. I think this can be closed. |
Sounds good.
This is correct for |
I see, getrandom is already an optional dependency of rand_core and rand though, so this sounds good too. |
@burdges in rust-random/rand#991:
The text was updated successfully, but these errors were encountered: