Jack O'Connor 05292a018b 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.)		2021-03-21 21:14:13 -04:00
..
workflows	get rid of the standalone "*_rayon" functions	2021-03-21 21:14:13 -04:00