| commit | 0a020ba4a37b8e2dec3da42584dbc0db97e1ddda | [log] [tgz] |
|---|---|---|
| author | Joel Galenson <jgalenson@google.com> | Wed Jun 09 20:22:04 2021 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jun 09 20:22:04 2021 +0000 |
| tree | 2c58548a32b572adf376984230f4061ef1449220 | |
| parent | 2376a5c41eb7e1de7d50c691fc3b5017ad5b804a [diff] | |
| parent | 3e7fe75dd7a0c529fc0b1a10ef9d3f657b023d40 [diff] |
Upgrade rust/crates/rayon-core to 1.9.1 am: 3e7fe75dd7 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/1713051 Change-Id: I97d1e08dab09f50b3cabfe098ce937ce80432594
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.