itsscb/uuid
1
0
Fork 0
mirror of https://github.com/uuid-rs/uuid.git synced 2026-04-23 16:48:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #804 from uuid-rs/fix/wasm-no-rng

Browse Source 
Add a compile_error when no source of randomness is available on wasm32-unknown-unknown
This commit is contained in:
Ashley Mannix
2025-02-15 09:39:03 +10:00
committed by GitHub
parent 54214179a6 bf28001d53
commit 7893ecce7f
3 changed files with 12 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -31,8 +31,6 @@ Add the following to your `Cargo.toml`:
version = "1.13.1"
features = [
"v4", # Lets you generate random UUIDs
"fast-rng", # Use a faster (but still sufficiently random) RNG
"macro-diagnostics", # Enable better diagnostics for compile-time UUIDs
]
```

10
src/lib.rs
View File

@@ -107,9 +107,11 @@
//! `borsh`.
//! * `arbitrary` - adds an `Arbitrary` trait implementation to `Uuid` for
//! fuzzing.
//! * `fast-rng` - uses a faster algorithm for generating random UUIDs.
//! * `fast-rng` - uses a faster algorithm for generating random UUIDs when available.
//! This feature requires more dependencies to compile, but is just as suitable for
//! UUIDs as the default algorithm.
//! * `rng-rand` - forces `rand` as the backend for randomness.
//! * `rng-getrandom` - forces `getrandom` as the backend for randomness.
//! * `bytemuck` - adds a `Pod` trait implementation to `Uuid` for byte manipulation
//!
//! # Unstable features
@@ -166,9 +168,9 @@
//! produce random bytes yourself and then pass them to [`Builder::from_random_bytes`]
//! without enabling the `v4` or `v7` features.
//!
//! Versions of `uuid` `1.12` or earlier relied on `getrandom` for randomness, this
//! is no longer guaranteed and configuring `getrandom`'s provider is not guaranteed
//! to make other features relying on randomness work.
//! If you're using `getrandom`, you can specify the `rng-getrandom` or `rng-rand`
//! features of `uuid` and configure `getrandom`'s provider per its docs. `uuid`
//! may upgrade its version of `getrandom` in minor releases.
//!
//! # Examples
//!

7
src/rng.rs
View File

@@ -1,4 +1,4 @@
#![allow(dead_code)] // Keeps our cfg's from becoming too convoluted in here
#![allow(dead_code, unused_imports)] // Keeps our cfg's from becoming too convoluted in here
trait Rng {
fn u128() -> u128;
@@ -100,8 +100,13 @@ mod imp {
Random support for `wasm32-unknown-unknown`.
*/
#![allow(dead_code, unused_imports)] // Keeps our cfg's from becoming too convoluted in here
use super::*;
#[cfg(all(not(feature = "js"), not(feature = "rng-getrandom"), not(feature = "rng-rand")))]
compile_error!("to use `uuid` on `wasm32-unknown-unknown`, specify a source of randomness using one of the `js`, `rng-getrandom`, or `rng-rand` features");
// Using `rand`
#[cfg(feature = "rng-rand")]
pub(super) struct RngImp;