commit | 2376a5c41eb7e1de7d50c691fc3b5017ad5b804a | [log] [tgz] |
---|---|---|
author | Bob Badour <bbadour@google.com> | Tue Mar 23 13:49:41 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Mar 23 13:49:41 2021 +0000 |
tree | 94d4ebfabd135e1221ef63e678539ffb5acb6c19 | |
parent | 1e8361e9b3fda01e83881027c39cd2584c1c9643 [diff] | |
parent | f473aca982fd65680ab6fae03bad9a88dd73ea6f [diff] |
[LSC] Add LOCAL_LICENSE_KINDS to external/rust/crates/rayon-core am: f473aca982 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/1650088 Change-Id: I12564649ce14daefb45f5146e54a6b8e9e08774f
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.