add #![no_std]

[AlexErrant]

Hi, total Rust noobie here; please assume the worst.

Does it make sense to add #![no_std] to this lib? Adding this doesn't seem to make any tests in this lib to fail, and there seems to be previous discussions in this repo suggesting that no_std is a goal.

The reason I ask is because I'm getting the following error in a downstream dep, Burn:

  = note: `std` is required by `const_random` because it does not declare `#![no_std]`

Cloning constrandom to my local machine, updating Burn's Cargo.toml to

const-random = { path = "../constrandom" }

and running the failing CI's command (cargo build -p burn --no-default-features --target wasm32-unknown-unknown --color=always) works on my local machine (when previously I could replicate the failure locally).

[AlexErrant]

Rearranging the deps in Burn resolved my error, but leaving this open in case it's still useful...?

[sleffler]

I'm trying to deal with fallout from this too.

Commit 4ef07e25a8b08153d527db84dd7f02d398ea1040 is what broke no_std support. This in turn broke my no_std usage of the hashbrown crate because I use ahash with the compile-time-rng feature which brings in const-random. (ahash pins const-random to 0.1.12 but because the maintainers yanked that version it appears the dep floats to the latest rev.)

The commit in question appears to be a cleanup so reverting it until there's a proper fix would seem to make sense. Otherwise restoring the old crate versions should work (dunno why they were purged).