tag | c8b6a0a3e73394f600eaedc84225caa788423112 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Wed May 08 00:18:06 2024 -0700 |
object | 10546d8c9ed9ae43874b2dc5785497771a868b9e |
Android CTS 14.0 Release 4 (11801623)
commit | 10546d8c9ed9ae43874b2dc5785497771a868b9e | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Apr 12 01:23:10 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Apr 12 01:23:10 2023 +0000 |
tree | ded15626a7744fe21c3f07d1e6d9230e28909490 | |
parent | c3daff3aaa76132fea0ee0440ab6e15cadb2833b [diff] | |
parent | 097a1e8e1828604e7a5f996ac7faad91ddb11c47 [diff] |
Snap for 9921839 from 097a1e8e1828604e7a5f996ac7faad91ddb11c47 to udc-release Change-Id: I0f35c705fc793873cae5c5f9704946b99f3d9b50
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.