| commit | 3431b891fb5a9b09e95b80fdfafbe0afd38ec910 | [log] [tgz] |
|---|---|---|
| author | Andrew Walbran <qwandor@google.com> | Mon Nov 13 00:17:42 2023 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Nov 13 00:17:42 2023 +0000 |
| tree | e41706de282a14c3b334590032cff5be83e69516 | |
| parent | fe0b55a60e98a89a83004413ece5fb156245b985 [diff] | |
| parent | 6c9f73a43e5a8f69540e53826066bb660154e891 [diff] |
Migrate to cargo_embargo. am: 2db8ca8f4b am: 6c9f73a43e Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/2824511 Change-Id: Ib74317087e296926a438599e262aac5cf7859cff 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.59.0 or greater.