commit | 05cfa5018b05dee5543234efb5dcf7d5ea3623b6 | [log] [tgz] |
---|---|---|
author | Matthew Maurer <mmaurer@google.com> | Thu Mar 09 15:13:05 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Mar 09 15:13:05 2023 +0000 |
tree | c0005587cc5dacd855a3692cfb14f76f0e558b42 | |
parent | f70dcdd3c96aab395be3403135200f4b72a307ed [diff] | |
parent | 946762913ba9a12eef97cb988cec04861986e511 [diff] |
Make rayon-core available to product and vendor am: 946762913b Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/2476292 Change-Id: I89333c9796ab7c5d10cc0eb81906c86bac1309e9 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.56.0
or greater.