commit | e62789713fd35921648b426d71005b6abf9deae2 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Jun 15 21:45:15 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Jun 15 21:45:15 2022 +0000 |
tree | 94d4ebfabd135e1221ef63e678539ffb5acb6c19 | |
parent | e687b4f6a70b104c131f968e0ff64a123352de43 [diff] | |
parent | c8c83ceeb6360a1d3d21d7e1bf53fd64699128bd [diff] |
Snap for 8730993 from c8c83ceeb6360a1d3d21d7e1bf53fd64699128bd to mainline-tzdata3-release Change-Id: I8928db4befe8651fe76d7b992ea0ad31c8f2123f
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.