| commit | fff30ca337a9ecf4a1be73d39c3d6a786a5cda5d | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Wed May 22 23:28:11 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Wed May 22 23:28:11 2024 +0000 |
| tree | 667865e857db3a0b8a6fbd3b8d0c653fe32072fc | |
| parent | 502870806131996dea2f65d86fddca9f758632cc [diff] | |
| parent | a67065820097765f687e9514ebd68948f033d89b [diff] |
Update Android.bp by running cargo_embargo am: 406c1dd659 am: a670658200 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/3096357 Change-Id: I43513293b25eab8d8de59c81f733edaf7497b214 Signed-off-by: Automerger Merge Worker <[email protected]>
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.63.0 or greater.