| commit | fa8c87e788cb0bd86d14ec8263c5257d08e2198f | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Tue Aug 27 23:06:06 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue Aug 27 23:06:06 2024 +0000 |
| tree | a83b84f512dd9ddd21a10fb5eab2bb705749ea9d | |
| parent | 7247addcafb507faa9172a020d0769872a1962d7 [diff] | |
| parent | b4e81462da861f8f88ce336e2dd4c3d0822cf080 [diff] |
Migrate 25 crates to monorepo. am: b4e81462da Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/fragile/+/3243723 Change-Id: I82472d79f61f0266b4e8b9660dfa8773c75a20a4 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();