| commit | bb6013c17ca71d3986af05c255eed1df4cf34d8d | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Wed Jun 19 04:26:06 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Wed Jun 19 04:26:06 2024 +0000 |
| tree | 287a55864b4a330c7c3895ad87af3d92203d629f | |
| parent | 2adf652661ca91c3eab94b69d69bd0f4e1cd7d6c [diff] | |
| parent | 7c40c6a02cc1fb36971d5d6fbd0b0f443b8e61e5 [diff] |
Snap for 11988867 from 7c40c6a02cc1fb36971d5d6fbd0b0f443b8e61e5 to 25D4-release Change-Id: Id8a7578bd41aac2fd1124311916784449be150d6
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();