commit | 30628deab525306a799417fc9c0a96a3764428db | [log] [tgz] |
---|---|---|
author | Joel Galenson <jgalenson@google.com> | Wed Dec 15 18:06:45 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Dec 15 18:06:45 2021 +0000 |
tree | 00997afec5942aa12d428a22e8e59c0bf76ec48e | |
parent | 80a448f5153e2eabbee89f3e6c683354667cf9e3 [diff] | |
parent | 2f4e4657a59ed74cfd16d5f85c0d6d440ffda228 [diff] |
Merge "Refresh Android.bp, cargo2android.json, TEST_MAPPING." am: 4d94ce0f2d am: 55f7d028b7 am: 8dc68158af am: 2f4e4657a5 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/1912651 Change-Id: I1e8c012b11985ddfbb6eddf4c7b9cab76550727f
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.