Did you mean point site:rust.docs.kernel.org?
5 matching pages, found in 90 ms
Ask StyxWritten on your GPU machine; takes a few seconds the first time.
-
rust.docs.kernel.orghttps://rust.docs.kernel.org › … › cell › lazy.rslazy.rs - source
More about rust.docs.kernel.org
… type in [`std::sync::poison`] like 27 /// [`std::sync::poison::Mutex`] allows recovery via [`PoisonError::into_inner()`]. 28 /// 29 /// [`force()`]: LazyCell::force 30 /// [`std::sync::poison`]: ../../std/sync/poison/index.html 31 /// [`std …
-
rust.docs.kernel.orghttps://rust.docs.kernel.org › core › cell › struct.LazyCellLazyCell in core::cell - Rust
More about rust.docs.kernel.org
… see std::sync::LazyLock . § Poisoning If the initialization closure passed to LazyCell::new panics, the cell will be poisoned. Once the cell is poisoned, any threads that attempt to access this cell …
-
rust.docs.kernel.orghttps://rust.docs.kernel.org › … › cell › struct.LazyCellLazyCell in core::cell - Rust
More about rust.docs.kernel.org
… see std::sync::LazyLock . § Poisoning If the initialization closure passed to LazyCell::new panics, the cell will be poisoned. Once the cell is poisoned, any threads that attempt to access this cell …
-
rust.docs.kernel.orghttps://rust.docs.kernel.org › … › panic › unwind_safe.rsunwind_safe.rs - source
More about rust.docs.kernel.org
… because they implement 75 /// poisoning by default. They still allow witnessing a broken invariant, but 76 /// they already provide their own "speed bumps" to do so. 77 /// 78 /// ## When should `UnwindSafe` be …
-
rust.docs.kernel.orghttps://rust.docs.kernel.org › … › panic › trait.UnwindSafeUnwindSafe in core::panic - Rust
More about rust.docs.kernel.org
… safe because they implement poisoning by default. They still allow witnessing a broken invariant, but they already provide their own “speed bumps” to do so. § When should UnwindSafe be used? It is …
Search for “Poison site:rust.docs.kernel.org” on Google, or add !ddg, !w and other shortcuts to any search.