commit | 4c940bdf041e3839434cac71fa9d7da3714e1fab | [log] [tgz] |
---|---|---|
author | Jakub Kotur <qtr@google.com> | Tue Mar 16 19:18:19 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Mar 16 19:18:19 2021 +0000 |
tree | 92ec3504482876b3cdf0915418c8d4b4f5191cd8 | |
parent | 7c5f66a679b75a8325d0775df538492947a1bd0d [diff] | |
parent | 1e8361e9b3fda01e83881027c39cd2584c1c9643 [diff] |
Add metadata files for rayon-core. am: 33dd7a40ec am: 1e8361e9b3 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/1621089 Change-Id: I826a0211ebe10504eb619e3dc9c2899744c4c3ae
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.