rand

https://github.com/BurntSushi/ripgrep https://github.com/rust-lang/hashbrown https://github.com/briansmith/ring https://github.com/rust-random/rand Lot of Rust programmers also coming from C, C++, and Go btw.

I'm not sure if I understand your wording: "a crate for seeding random number generators"? Do you mean, "is there a RNG that you can seed in Rust"? There's a `rand` crate[0] which I believe was written by folks in the Rust project, though it's not part of std. You can seed the RNG[1]. [0] https://crates.io/crates/rand, https://github.com/rust-random/rand [1] https://docs.rs/rand/latest/rand/rngs/struct.StdRng.html#met...

This is a widely used method to map random integers to floating point numbers, but it has the disadvantage of wasting 1 bit of float mantissa precision. On modern CPUs, its computational advantage over full-precision mapping methods, such as multiplication by a float, is not always clear [1]. [1] https://github.com/rust-random/rand/issues/416

That's an application, not a library though. There's really no reason for an application not to require the latest compiler version if they so choose. There are definitely libraries that take this approach too, but they tend to be higher-level domain-specific ones. The foundational libraries in the ecosystem tend to take a much more conservative approach to MSRV (minimum supported rust version), supporting older Rust versions for as long as possible, and only bumping the version when new features that significantly improve the library are released (and often only once the versions implementing those features are packaged in stable releases of major distros). For example, the `rand` crate supports Rust versions down to 1.36 (released in July 2019) [0], the regex crate supports down to 1.41.1 (released Feb 2020) [1], etc. [0]: https://githu