commit | 32b0d808bc62062e694b3bee27a0039b3223e324 | [log] [tgz] |
---|---|---|
author | Joel Galenson <jgalenson@google.com> | Wed Jun 09 21:17:20 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jun 09 21:17:20 2021 +0000 |
tree | 2c58548a32b572adf376984230f4061ef1449220 | |
parent | 5b314a6474a13d54bef0791ccaa63b3860eb4ec9 [diff] | |
parent | 023bd149ea857e3b50ab9f6f8d5c421c9a4c729f [diff] |
Upgrade rust/crates/rayon-core to 1.9.1 am: 3e7fe75dd7 am: 0a020ba4a3 am: f14cfd80ef am: 023bd149ea Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/1713051 Change-Id: Idc3e86a2b2cf722d98d464fb4d535e0a12732751
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.