commit | 882ea449d0b622b049b2924ae059b1938ade5c82 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Dec 16 02:07:28 2021 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Dec 16 02:07:28 2021 +0000 |
tree | 00997afec5942aa12d428a22e8e59c0bf76ec48e | |
parent | 40fccb9f462babab58cd897c6ebc41cdfbb036a4 [diff] | |
parent | 30628deab525306a799417fc9c0a96a3764428db [diff] |
Snap for 8006021 from 30628deab525306a799417fc9c0a96a3764428db to tm-release Change-Id: Id787f330c477841ed45afef186a590acdeb1d356
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.