Google Git
Sign in
android / platform / external / rust / crates / rayon-core / refs/heads/main
commit682771a8de10e8857e4ae071b7799072ddf88a8e[log] [tgz]
authorJeff Vander Stoep <jeffv@google.com>Wed Feb 07 09:28:17 2024 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Feb 07 09:28:17 2024 +0000
treec23f768a86f6dec3105f8f8420f4b742e9cf3044
parent12bfc0b2e2bdbaa7b92f3934096e1371143f5797 [diff]
parent96905156f39d29938fabf7cb278c4f8c52955af5 [diff]
Upgrade rayon-core to 1.12.1 am: 96905156f3

Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/rayon-core/+/2952887

Change-Id: I976cf18aeca6eafc5680194c3b5151837875c73d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: c23f768a86f6dec3105f8f8420f4b742e9cf3044
  1. src/
  2. tests/
  3. LICENSE ⇨ LICENSE-APACHE
  4. .cargo_vcs_info.json
  5. Android.bp
  6. build.rs
  7. Cargo.toml
  8. Cargo.toml.orig
  9. cargo_embargo.json
  10. LICENSE-APACHE
  11. LICENSE-MIT
  12. METADATA
  13. MODULE_LICENSE_APACHE2
  14. OWNERS
  15. README.md
  16. TEST_MAPPING
README.md

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.