From bc7a2d72a3fea324fa432de9b6ce6073302d3d8c Mon Sep 17 00:00:00 2001 From: Huon Wilson Date: Tue, 25 Mar 2014 16:13:11 +1100 Subject: rand: bubble up IO messages futher. The various ...Rng::new() methods can hit IO errors from the OSRng they use, and it seems sensible to expose them at a higher level. Unfortunately, writing e.g. `StdRng::new().unwrap()` gives a much poorer error message than if it failed internally, but this is a problem with all `IoResult`s. --- src/libcollections/deque.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/libcollections') diff --git a/src/libcollections/deque.rs b/src/libcollections/deque.rs index 05df04d293f..6fd525bac2e 100644 --- a/src/libcollections/deque.rs +++ b/src/libcollections/deque.rs @@ -52,7 +52,7 @@ pub mod bench { map: &mut M, bh: &mut BenchHarness) { // setup - let mut rng = rand::XorShiftRng::new(); + let mut rng = rand::weak_rng(); map.clear(); for _ in range(0, n) { @@ -89,7 +89,7 @@ pub mod bench { map: &mut M, bh: &mut BenchHarness) { // setup - let mut rng = rand::XorShiftRng::new(); + let mut rng = rand::weak_rng(); let mut keys = slice::from_fn(n, |_| rng.gen::() % n); for k in keys.iter() { -- cgit 1.4.1-3-g733a5