commit | dc1fefbea0a4d65d39123bcd55b521a683882fb6 | [log] [tgz] |
---|---|---|
author | Joel Galenson <jgalenson@google.com> | Mon Aug 30 20:52:00 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Aug 30 20:52:00 2021 +0000 |
tree | ad99dc20ef40743400a48c6dbadb8bf16c8e57ff | |
parent | f14cfd80ef571a5fbfe751cf670a6c424f72fc2f [diff] | |
parent | d352fba4e3a63f1562c70eab571594ed712a9453 [diff] |
Update TEST_MAPPING am: d352fba4e3 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/1813860 Change-Id: I2dc0e753b85209f2bdb987ce90ce0691cbbd7ab1
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.