commit | 76bb06a2cbd0ffeb39b01190bfc7ef87bf44ecbd | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Wed Mar 24 01:05:37 2021 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Wed Mar 24 01:05:37 2021 +0000 |
tree | 94d4ebfabd135e1221ef63e678539ffb5acb6c19 | |
parent | fddcd2e80e8c63e05156694ac1715f3d92c471c8 [diff] | |
parent | ed0b52af89cf7eba357ad0b9267d1f62ab4ffd7a [diff] |
Snap for 7230642 from ed0b52af89cf7eba357ad0b9267d1f62ab4ffd7a to sc-v2-release Change-Id: I6db4cc0a1cb9ebd65f2404e7c340968210ae7ab2
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.