| commit | 875d66d73b95b522a42cfd9a6aa64cb1e0f0b007 | [log] [tgz] |
|---|---|---|
| author | Oliver Middleton <olliemail27@gmail.com> | Fri Jun 24 23:15:58 2016 +0100 |
| committer | Oliver Middleton <olliemail27@gmail.com> | Fri Jun 24 23:26:42 2016 +0100 |
| tree | 94a0f4d3ff1e54a03e016fa11dcf56c3cba4c3c3 | |
| parent | 9f35b8e439eeedd60b9414c58f389bdc6a3284f9 [diff] |
Revert "Ignore should_panic tests on MSVC" This reverts commit 557c30d0897b8c22f594f3af8571b7c630fbb407. This was presumably from when i686 didn't support panics but it has for a long time now so we may as well reenable these tests.
A Rust library for random number generators and other randomness functionality.
Add this to your Cargo.toml:
[dependencies] rand = "0.3"
and this to your crate root:
extern crate rand;
There is built-in support for a random number generator (RNG) associated with each thread stored in thread-local storage. This RNG can be accessed via thread_rng, or used implicitly via random. This RNG is normally randomly seeded from an operating-system source of randomness, e.g. /dev/urandom on Unix systems, and will automatically reseed itself from this source after generating 32 KiB of random data.
let tuple = rand::random::<(f64, char)>(); println!("{:?}", tuple)
use rand::Rng; let mut rng = rand::thread_rng(); if rng.gen() { // random bool println!("i32: {}, u32: {}", rng.gen::<i32>(), rng.gen::<u32>()) }
It is also possible to use other RNG types, which have a similar interface. The following uses the “ChaCha” algorithm instead of the default.
use rand::{Rng, ChaChaRng}; let mut rng = rand::ChaChaRng::new_unseeded(); println!("i32: {}, u32: {}", rng.gen::<i32>(), rng.gen::<u32>())