commit | 8dc68158af0b4d7ca068b620aacf3acf91bd68fc | [log] [tgz] |
---|---|---|
author | Joel Galenson <jgalenson@google.com> | Wed Dec 15 16:43:07 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Dec 15 16:43:07 2021 +0000 |
tree | 00997afec5942aa12d428a22e8e59c0bf76ec48e | |
parent | 1dbe5a8cfae0bf1786f5832dffbbe229b8e4d10e [diff] | |
parent | 55f7d028b7a3646633ffea7cdd36c48d30cf023e [diff] |
Merge "Refresh Android.bp, cargo2android.json, TEST_MAPPING." am: 4d94ce0f2d am: 55f7d028b7 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/1912651 Change-Id: I91216d79e51b4a3eb89b98e1d975e222e90eb7ea
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.