cuviper on rayon-core-v1.10.2
bors[bot] on master
Release rayon-core 1.10.2 Merge #1013 1013: Release rayo… (compare)
bors[bot] on staging.tmp
bors[bot] on staging
Release rayon-core 1.10.2 Merge #1013 1013: Release rayo… (compare)
bors[bot] on staging.tmp
Release rayon-core 1.10.2 [ci skip][skip ci][skip netlify… (compare)
bors[bot] on staging.tmp
[ci skip][skip ci][skip netlify] (compare)
bors[bot] on master
Use pointers instead of `&self`… Add a virtual wrapper for &Latch Merge #1011 1011: Use pointers… (compare)
bors[bot] on staging.tmp
bors[bot] on staging
Use pointers instead of `&self`… Add a virtual wrapper for &Latch Merge #1011 1011: Use pointers… (compare)
bors[bot] on staging.tmp
[ci skip][skip ci][skip netlify] (compare)
bors[bot] on staging.tmp
Use pointers instead of `&self`… Add a virtual wrapper for &Latch [ci skip][skip ci][skip netlify… (compare)
ThreadPool
each time)
perf
, if that helps
for
loops are hard-coded to the regular Iterator
trait
Iterator::for_each
, then this can translate to ParallelIterator::for_each
out
vector to &mut [AtomicI8]
.
(0..data.len()).into_par_iter().for_each(|i| /* atomic store */)
@jntrnr https://is.gd/QFQpOF
If I'm reading this right, you're saying to break into blocks that are outside of rayon? How would you know what size to split into so that rayon is efficient? Feels like something rayon should do so that it's able to tune for efficiency
rng::thread_rng()
and pass a Sender
to a for_each
loop. Unfortunately for_each_init
requires Sync
as a trait bound, which is not satisfied by Sender
. Is there a way to get both, the functionality of for_each_init
and for_each_with
at the same time?