tag | 5590af345fb78285355672997cf5505e1e6500bf | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Tue May 07 10:58:41 2024 -0700 |
object | 64cfc8297a973643de1e9d37b9767337056440e0 |
Android 14.0.0 release 37
commit | 64cfc8297a973643de1e9d37b9767337056440e0 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue Nov 14 00:13:33 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue Nov 14 00:13:33 2023 +0000 |
tree | e41706de282a14c3b334590032cff5be83e69516 | |
parent | 5f640225322343c2adb5c9a2440bec536075abe9 [diff] | |
parent | 12bfc0b2e2bdbaa7b92f3934096e1371143f5797 [diff] |
Snap for 11089623 from 12bfc0b2e2bdbaa7b92f3934096e1371143f5797 to 24Q1-release Change-Id: I7cac179b0c897cb1255fd79b0da2db064c0084dc
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.