commit | 17bacfac113e13fb3a3a94866640224d921324a4 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Oct 28 17:30:28 2021 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Oct 28 17:30:28 2021 +0000 |
tree | ad99dc20ef40743400a48c6dbadb8bf16c8e57ff | |
parent | 06fc066c7460def2c705a7fb28ff838e1e58a91e [diff] | |
parent | a079b300b05260e398e3dec559b9957c43b9922d [diff] |
Snap for 7862349 from a079b300b05260e398e3dec559b9957c43b9922d to t-keystone-qcom-release Change-Id: If1a6d298336a358e82089239d0affb01f838ca45
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.