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

Seems that vigna (author of the xoshiro family of rngs) mostly agrees with you > Personally, I don't believe in the "middle ground" of "difficult-to-predict-but-not-crypto": usually it just means it is so easy to break that nobody https://github.com/rust-random/rand/issues/905#issuecomment-...

It’s spreading https://github.com/rust-random/rand/issues/1172

Book is what this site layout is called in the community, see also: Rust Book: https://doc.rust-lang.org/book Rust Rand Book: https://rust-random.github.io/book Rust WebAssembly Book: https://rustwasm.github.io/book Rust Unstable Book: https://doc.rust-lang.org/beta/unstable-book/index.html Rustonomicon: https://doc.rust-lang.org/beta/nomicon/index.html Cargo Book: https://doc.rust-lang.org/cargo Which seems to be generated by https://github.com/rust-lang/mdBook Now, I don't see why "book" should seem so grand. Remember when reference books would come out as a "bible"? As for bounds check, here's a relevant issue raised on rand crate: https://github.com/rust-random/rand/issues/592 One can dig for a kind of "unsafe assertions" with https://doc.rust-lang.org/std/hint/fn.unreachable_unchecked.... (so the random code, for example, could have

Hm, appears to be an alternate (new? Old?) syntax for: "Cargo will take the latest commit and write that information out into our Cargo.lock when we build for the first time. That file will look like this: [[package]] name = "hello_world" version = "0.1.0" dependencies = [ "rand 0.1.0 (git+https://github.com/rust-lang-nursery/rand.git#9f35b8e439eeed..., ] [[package]] name = "rand" version = "0.1.0" source = "git+https://github.com/rust-lang-nursery/rand.git#9f35b8e439eeed... You can see that there’s a lot more information here, including the exact revision we used to build."

So, at first, it will compile, but fail: https://github.com/rust-lang-nursery/rand/pull/197 Then, two weeks ago https://github.com/rust-lang-nursery/rand/pull/272 > Would anything that depended on that need to use a random function from js instead? Your instinct is right, that's what the above does. (more specifically, with https://developer.mozilla.org/en-US/docs/Web/API/RandomSourc... )