| commit | 27119c99d02b711f8a2f463111e24dffc5f72463 | [log] [tgz] |
|---|---|---|
| author | Xin Li <[email protected]> | Mon May 13 10:33:28 2024 -0700 |
| committer | Xin Li <[email protected]> | Mon May 13 13:14:51 2024 -0700 |
| tree | 63304b1ef3a96d0cbde883bdebb3cea3fd227863 | |
| parent | 6263fa3a2c057e7b5b193eb80fc84dba936ec920 [diff] | |
| parent | 0916c5f23fd03f6758987f7a095e680a356be0d1 [diff] |
Merge Android 24Q2 Release (ab/11526283) to aosp-main-future Bug: 337098550 Merged-In: Ia0d57705ea79edf5232d2932b12d554fa4d13372 Change-Id: I2508c2e6a628154cfd06aa97fcc7a8eeb0a7a315
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();