[automerger skipped] Empty merge of Android 24Q2 Release (ab/11526283) to aosp-main-future am: a34c9c09c7 -s ours am skip reason: Merged-In Idf88a8335e8856f3a2933a3bfbcdf7c1e4db1af5 with SHA-1 ffc4a5b6cd is already in history Original change: https://googleplex-android-review.googlesource.com/c/platform/external/rust/crates/atomic/+/27144128 Change-Id: I3132acd22d638b2551edd5e1cc8423b42b6e2681 Signed-off-by: Automerger Merge Worker <[email protected]>
Atomic<T> for RustA Rust library which provides a generic Atomic<T> type for all T: NoUninit types, unlike the standard library which only provides a few fixed atomic types (AtomicBool, AtomicIsize, AtomicUsize, AtomicPtr). The NoUninit bound is from the bytemuck crate, and indicates that a type has no internal padding bytes. You will need to derive or implement this trait for all types used with Atomic<T>.
This library will use native atomic instructions if possible, and will otherwise fall back to a lock-based mechanism. You can use the Atomic::<T>::is_lock_free() function to check whether native atomic operations are supported for a given type. Note that a type must have a power-of-2 size and alignment in order to be used by native atomic instructions.
This crate uses #![no_std] and only depends on libcore.
Add this to your Cargo.toml:
[dependencies] atomic = "0.6"
and this to your crate root:
extern crate atomic;
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.