tag | bf9f63bf00dcc1faa592eb2f6eb9741a60a88c95 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Thu May 19 16:25:56 2022 -0700 |
object | 3fd69d0aacbd8249df358a5e9130568fcfe24cd7 |
Platform Tools Release 33.0.1 (8253317)
commit | 3fd69d0aacbd8249df358a5e9130568fcfe24cd7 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Dec 16 00:04:18 2021 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Dec 16 00:04:18 2021 +0000 |
tree | 00997afec5942aa12d428a22e8e59c0bf76ec48e | |
parent | bf0252185c82de4bc3df653dd4910a7c5f3a5b01 [diff] | |
parent | 4d94ce0f2d30ae520f46a899d8fceb6a36be57e5 [diff] |
Snap for 8005954 from 4d94ce0f2d30ae520f46a899d8fceb6a36be57e5 to sdk-release Change-Id: I5a7b86f13269fb50f1fee5354273830d5c1518a1
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.