commit | 9b87d9fb335467874dbc180e35c9c6c073507225 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Jan 31 01:51:04 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Jan 31 01:51:04 2022 +0000 |
tree | 00997afec5942aa12d428a22e8e59c0bf76ec48e | |
parent | 17bacfac113e13fb3a3a94866640224d921324a4 [diff] | |
parent | e5cf90b0a68b294425fec22de7017826b0211eb5 [diff] |
Snap for 8133678 from e5cf90b0a68b294425fec22de7017826b0211eb5 to t-keystone-qcom-release Change-Id: I4baf4b4277a830ccbeca0a354858b5278cd5d7bd
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.