| commit | 88cc6d0a2ab63d6591df44b05c9abce3cee25ea0 | [log] [tgz] |
|---|---|---|
| author | Wei Li <[email protected]> | Mon Aug 05 23:44:20 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Mon Aug 05 23:44:20 2024 +0000 |
| tree | 2dbe03b5ef94364d6d9de7b8be7054d2c550deb1 | |
| parent | 6c31927a2ffc3320318b5f3ee7909d830262e693 [diff] | |
| parent | 8f656cb0af1dffecb75b646ed845f70a81cc8cdb [diff] |
Cleanup license metadata in external/rust/crates/fragile. am: 8f656cb0af Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/fragile/+/3206931 Change-Id: Ifabd3e1aea06f169cfee382a611e625eb01f914a 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();