From 5ecd1e9e00c039e0490f35a161024d75e8739533 Mon Sep 17 00:00:00 2001 From: Naja Melan Date: Thu, 15 Aug 2019 09:43:23 +0200 Subject: [PATCH] Make the documentation for WASM targets clearer For people who run in a compile error because `wasm-bindgen` or `stdweb` features are not enabled, clarify that they can enable it even if getrandom gets pulled in by one of their dependencies. --- src/lib.rs | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/lib.rs b/src/lib.rs index 104ec4415..bfb146075 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -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. +//! //! The WASI target `wasm32-wasi` uses the `__wasi_random_get` function defined //! by the WASI standard. //!