commit | 05adef1b681e15da9f33e35789ffddbcbdd8593a | [log] [tgz] |
---|---|---|
author | Linux Build Service Account <lnxbuild@localhost> | Wed Feb 16 21:42:10 2022 -0800 |
committer | Linux Build Service Account <lnxbuild@localhost> | Wed Feb 16 21:42:10 2022 -0800 |
tree | 00997afec5942aa12d428a22e8e59c0bf76ec48e | |
parent | 17bacfac113e13fb3a3a94866640224d921324a4 [diff] | |
parent | 9b87d9fb335467874dbc180e35c9c6c073507225 [diff] |
Merge 9b87d9fb335467874dbc180e35c9c6c073507225 on remote branch Change-Id: I99a5477cb03f3bef965ffd4df823ba069acb3b97
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.