| commit | 1cbbebdbe827c5ac6b4ba1e770f42911c155a940 | [log] [tgz] |
|---|---|---|
| author | Linux Build Service Account <lnxbuild@localhost> | Sun Jan 16 14:31:13 2022 -0800 |
| committer | Linux Build Service Account <lnxbuild@localhost> | Sun Jan 16 14:31:13 2022 -0800 |
| tree | 94d4ebfabd135e1221ef63e678539ffb5acb6c19 | |
| parent | 090ab4c4072d2e2f6b523220e1489a14648dbdec [diff] | |
| parent | ad805279d13325dac82cfde4f397e6edb608b902 [diff] |
Merge ad805279d13325dac82cfde4f397e6edb608b902 on remote branch Change-Id: I2e1a5aa10c27e519632779fb580add2c7119efe2
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.36.0 or greater.