5 unstable releases

0.3.0 Oct 7, 2019
0.2.0 Apr 25, 2019
0.1.2 Jan 31, 2019
0.1.1 Jun 6, 2018
0.1.0 May 10, 2018

#34 in Concurrency

Download history 8916/week @ 2019-06-24 7474/week @ 2019-07-01 5928/week @ 2019-07-08 5644/week @ 2019-07-15 6233/week @ 2019-07-22 6389/week @ 2019-07-29 5794/week @ 2019-08-05 6390/week @ 2019-08-12 5257/week @ 2019-08-19 6054/week @ 2019-08-26 6400/week @ 2019-09-02 5632/week @ 2019-09-09 5876/week @ 2019-09-16 5783/week @ 2019-09-23 6460/week @ 2019-09-30

25,558 downloads per month
Used in 29 crates (3 directly)

Apache-2.0/MIT

200KB
3.5K SLoC

Note: This is an unstable fork made for use in rustc

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.


lib.rs:

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.

Dependencies

~455KB