| commit | e14b43c4f1c44c37ec7747f0c411f3acf7a3aae3 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Tue Aug 06 23:13:08 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Tue Aug 06 23:13:08 2024 +0000 |
| tree | 2dbe03b5ef94364d6d9de7b8be7054d2c550deb1 | |
| parent | bb6013c17ca71d3986af05c255eed1df4cf34d8d [diff] | |
| parent | 301a04a3ce8181e9390ce86e8bc0fbf270a63528 [diff] |
Snap for 12190251 from 301a04a3ce8181e9390ce86e8bc0fbf270a63528 to 25D4-release Change-Id: I4e32cc13fcdff5f0242dc858b75fb60cce2b8cff
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();