commit | beb960dd4899ee5905a34c0e8692b2947875646f | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue May 10 07:05:30 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue May 10 07:05:30 2022 +0000 |
tree | 00997afec5942aa12d428a22e8e59c0bf76ec48e | |
parent | c8c83ceeb6360a1d3d21d7e1bf53fd64699128bd [diff] | |
parent | 30628deab525306a799417fc9c0a96a3764428db [diff] |
Snap for 8564071 from 30628deab525306a799417fc9c0a96a3764428db to mainline-wifi-release Change-Id: Iad12032e12060f7d945e0e331196f1487739d651
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.