| commit | 29340a3b1372364731c3882d8e86a6f8683a9d4e | [log] [tgz] |
|---|---|---|
| author | Xin Li <[email protected]> | Thu Jun 13 10:50:01 2024 -0700 |
| committer | Xin Li <[email protected]> | Thu Jun 13 10:50:01 2024 -0700 |
| tree | 287a55864b4a330c7c3895ad87af3d92203d629f | |
| parent | de2760252424cdf83b7c2ac4fd8a00a1f17b6bd9 [diff] | |
| parent | 7962cffe9217a50aa5bd960e905cf6287ea294e0 [diff] |
Merge Android 14 QPR3 to AOSP main Bug: 346855327 Merged-In: I817e75522d896e5c5b01bac5b5d174b0654dbac1 Change-Id: I2d004eb3cb2a342b869fe223edc91aea91b85805
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();