commit | ecec3053e344f9a90a9b055bf28dad7c56719407 | [log] [tgz] |
---|---|---|
author | Jeff Vander Stoep <jeffv@google.com> | Mon Jan 30 13:15:04 2023 +0100 |
committer | Jeff Vander Stoep <jeffv@google.com> | Mon Jan 30 13:15:04 2023 +0100 |
tree | bd76d1523ac3d904cd5e4bfd73ad78ca0a26d471 | |
parent | acae64b67d72444b74af5db45f6836ff73f49605 [diff] |
Update TEST_MAPPING Test: atest Change-Id: I5d2f2f2692f7547c7379d72f94b66577a978cb7b
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.56.0
or greater.