commit | 946762913ba9a12eef97cb988cec04861986e511 | [log] [tgz] |
---|---|---|
author | Matthew Maurer <mmaurer@google.com> | Tue Mar 07 17:24:40 2023 -0800 |
committer | Matthew Maurer <mmaurer@google.com> | Tue Mar 07 17:24:40 2023 -0800 |
tree | c0005587cc5dacd855a3692cfb14f76f0e558b42 | |
parent | e27ffc4ea6455b714614a8bdab40aaafb02253ac [diff] |
Make rayon-core available to product and vendor Bug: 270690570 Test: mma in external/rust/crates Change-Id: I105340842721676bfe3972eb5f5bdec2b5d68496
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.56.0
or greater.