| commit | 26e8daaaf279e05da2c077d7009f64c1747a0ed5 | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Tue May 21 15:04:01 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue May 21 15:04:01 2024 +0000 |
| tree | 287a55864b4a330c7c3895ad87af3d92203d629f | |
| parent | 3edf35698a8c815b4f5dabff767f32800f4bc29d [diff] | |
| parent | 7962cffe9217a50aa5bd960e905cf6287ea294e0 [diff] |
Update Android.bp by running cargo_embargo am: de27602524 am: 7962cffe92 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/fragile/+/3095105 Change-Id: Ic29221292236db36e372bdbae64c11b71f2b562a Signed-off-by: Automerger Merge Worker <[email protected]>
This library provides wrapper types that permit sending non Send types to other threads and use runtime checks to ensure safety.
It provides the Fragile<T>, Sticky<T> and SemiSticky<T> types which are similar in nature but have different behaviors with regards to how destructors are executed. The Fragile<T> will panic if the destructor is called in another thread, Sticky<T> will temporarily leak the object until the thread shuts down. SemiSticky<T> is a compromise of the two. It behaves like Sticky<T> but it avoids the use of thread local storage if the type does not need Drop.
use std::thread; // creating and using a fragile object in the same thread works let val = Fragile::new(true); assert_eq!(*val.get(), true); assert!(val.try_get().is_ok()); // once send to another thread it stops working thread::spawn(move || { assert!(val.try_get().is_err()); }).join() .unwrap();