Skip to content

Make the documentation for WASM targets clearer #89

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.

Sign up for GitHub

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

Closed
najamelan wants to merge 1 commit into from
Closed

Make the documentation for WASM targets clearer #89

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions src/lib.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,10 @@
//! by enabling the `dummy` feature, which will make `getrandom` to use an
//! always failing implementation.
//!
//! If you are seeing this compiler error even though your crate doesn't directly
//! depend on getrandom (one of your dependencies pulls it in), you can still solve
//! this by adding getrandom as a dependency to your `Cargo.toml` with the correct feature.
Copy link
Copy Markdown
Member

@newpavlov newpavlov Aug 15, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think there is the feature to be enabled. Also please take a look at #87. I am not sure if enabling dummy, stdweb or wasm-bindgen feature in an non-application Cargo.toml is a correct recommendation.

//!
//! The WASI target `wasm32-wasi` uses the `__wasi_random_get` function defined
//! by the WASI standard.
//!
Expand Down
⚡