Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
512: Allow v3, v4, v5 features on wasm32-unknown-unknown r=kinggoesgaming a=Expyron I'm submitting a feature # Description The v3, v4, v5 features did not work on `wasm32-unknown-unknown` in a no_std context. For v3 and v5, the `md5` and `sha1` crates are no_std if their default features are disabled, so they work on `wasm32-unknown-unknown`. For v4, `getrandom` can work on any architecture if the root crate registers a custom implementation. This is not a breaking change, as the other architectures (including `stdweb` and `wasm-bindgen`) are not impacted. # Motivation I wanted to use this crate (especially the v4 feature) on a `wasm32-unknown-unknown` context that does not have `stdweb` nor `wasm-bindgen`. # Tests The test suite unfortunately does not run on `wasm32-unknown-unknown`. The v3, v4, v5 features work properly, as I was able to use them from a dependent crate. Co-authored-by: Expyron <Expyron@users.noreply.github.com>
- Loading branch information
Showing
3 changed files
with
10 additions
and
35 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters