| commit | f70dcdd3c96aab395be3403135200f4b72a307ed | [log] [tgz] |
|---|---|---|
| author | Jeff Vander Stoep <jeffv@google.com> | Fri Feb 17 20:08:51 2023 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Feb 17 20:08:51 2023 +0000 |
| tree | 726fe77ff8ed6a97c897ec126a4a93427f002ff6 | |
| parent | ea4058fb0315a4e8405344deac75b43db078fa74 [diff] | |
| parent | e27ffc4ea6455b714614a8bdab40aaafb02253ac [diff] |
Upgrade rayon-core to 1.10.2 am: e27ffc4ea6 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/2441423 Change-Id: I2a22bc3a46850b1dcec0b24a779fddd4f73530af 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.