10 stable releases

1.6.0 Aug 31, 2019
1.5.0 Jun 13, 2019
1.4.1 Jul 17, 2018
1.4.0 Feb 15, 2018
0.0.1 Mar 11, 2017

#25 in Concurrency

Download history 43305/week @ 2019-05-18 47138/week @ 2019-05-25 48874/week @ 2019-06-01 52855/week @ 2019-06-08 56634/week @ 2019-06-15 59480/week @ 2019-06-22 52737/week @ 2019-06-29 50443/week @ 2019-07-06 47551/week @ 2019-07-13 50185/week @ 2019-07-20 50666/week @ 2019-07-27 54607/week @ 2019-08-03 54117/week @ 2019-08-10 53966/week @ 2019-08-17 55117/week @ 2019-08-24

226,200 downloads per month
Used in 1,216 crates (3 directly)



Rayon-core represents the "core, stable" APIs of Rayon: join, scope, and so forth, as well as the ability to create custom thread-pools with ThreadPool.

Maybe worth mentioning: users are not necessarily intended to directly access rayon-core; all its APIs are mirror in the rayon crate. To that end, the examples in the docs use rayon::join and so forth rather than rayon_core::join.

rayon-core aims to never, or almost never, have a breaking change to its API, because each revision of rayon-core also houses the global thread-pool (and hence if you have two simultaneous versions of rayon-core, you have two thread-pools).

Please see Rayon Docs for details about using Rayon.

Rayon-core currently requires rustc 1.28.0 or greater.


Under construction

Restricting multiple versions

In order to ensure proper coordination between threadpools, and especially to make sure there's only one global threadpool, rayon-core is actively restricted from building multiple versions of itself into a single target. You may see a build error like this in violation:

error: native library `rayon-core` is being linked to by more
than one package, and can only be linked to by one package

While we strive to keep rayon-core semver-compatible, it's still possible to arrive at this situation if different crates have overly restrictive tilde or inequality requirements for rayon-core. The conflicting requirements will need to be resolved before the build will succeed.