get rid of the standalone "*_rayon" functions

These clutter the toplevel API, and their prominence might lead callers
to prefer them as a first resort, which probably isn't a good idea.
Restricting multithreading to `Hasher::update_rayon` feels better,
similar to what we've done with `Hasher::finalize_xof`. (But I think
`update_rayon` is still an improvement over the trait-based interface
that it replaced.)

1 files changed, 1 insertions, 1 deletions

diff --git a/benches/bench.rs b/benches/bench.rs
index 832f0f8..90dbc42 100644
--- a/benches/bench.rs
+++ b/benches/bench.rs
@@ -421,7 +421,7 @@ fn bench_reference_1024_kib(b: &mut Bencher) {
 #[cfg(feature = "rayon")]
 fn bench_rayon(b: &mut Bencher, len: usize) {
     let mut input = RandomInput::new(b, len);
-    b.iter(|| blake3::hash_rayon(input.get()));
+    b.iter(|| blake3::Hasher::new().update_rayon(input.get()).finalize());
 }
 
 #[bench]