commit | 80a448f5153e2eabbee89f3e6c683354667cf9e3 | [log] [tgz] |
---|---|---|
author | Joel Galenson <jgalenson@google.com> | Mon Aug 30 22:09:42 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Aug 30 22:09:42 2021 +0000 |
tree | ad99dc20ef40743400a48c6dbadb8bf16c8e57ff | |
parent | 32b0d808bc62062e694b3bee27a0039b3223e324 [diff] | |
parent | a7865d9a1b40349a8adda6a844806685099bf157 [diff] |
Update TEST_MAPPING am: d352fba4e3 am: dc1fefbea0 am: da314a0aa7 am: 1dbe5a8cfa am: a7865d9a1b Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/1813860 Change-Id: Icdeaa5f6717839f6abe6c971e79fe9ec79e1f43a
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.