Google Git
Sign in
android / platform / external / rust / crates / rayon-core / refs/heads/main
commit3c7af9b9b906e3e7cea0c7b4f97a52b8c9d3f4d4[log] [tgz]
authorJames Farrell <jamesfarrell@google.com>Thu Aug 29 16:00:30 2024 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Thu Aug 29 16:00:30 2024 +0000
tree6720801fb8cb497343e338a28bc3b90bcee7739a
parent45ae654a4bf93e3c78e796b0fe05d05accc314d5 [diff]
parentee7ec2f6b630f197dcccfbf7c12f368edbc5383f [diff]
Migrate 25 crates to monorepo. am: ee7ec2f6b6

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

Change-Id: Ibbbf887746d20f0b9de4aa27dd9745168b8e0d83
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: 6720801fb8cb497343e338a28bc3b90bcee7739a
  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. LICENSE-APACHE
  10. LICENSE-MIT
  11. METADATA
  12. MODULE_LICENSE_APACHE2
  13. OWNERS
  14. README.md
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.