tag | 3a7f98d13d0dd114ebe224b3c30049ddcc3a3b20 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Wed Apr 24 20:11:03 2024 -0700 |
object | 1b003593ebfe17b8269cdbb5be6cb2c56bf259cc |
aml_wif_341610000 (11391728,com.google.android.wifi)
commit | 1b003593ebfe17b8269cdbb5be6cb2c56bf259cc | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Jul 07 01:05:03 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Jul 07 01:05:03 2023 +0000 |
tree | ded15626a7744fe21c3f07d1e6d9230e28909490 | |
parent | beb960dd4899ee5905a34c0e8692b2947875646f [diff] | |
parent | f110d982be1a009b2da88e6feeeb261762daa4dc [diff] |
Snap for 10447354 from f110d982be1a009b2da88e6feeeb261762daa4dc to mainline-wifi-release Change-Id: If0ed86c02f07034d2480b3033344302a062608f4
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.59.0
or greater.