rust/library/std/src/sync, branch try

Update poison.rs

2025-07-16T03:07:03+00:00

Typo in word "below"

Rollup merge of #143340 - nabijaczleweli:awhile, r=mati865

2025-07-07T17:55:32+00:00

awhile -> a while where appropriate

Rollup merge of #143086 - SciMind2460:patch-2, r=workingjubilee

2025-07-05T06:26:20+00:00

Update poison.rs to fix the typo (sys->sync)

awhile -> a while where appropriate

2025-07-02T18:17:29+00:00

Update version placeholders

2025-07-01T17:54:33+00:00

Update poison.rs to fix the typo (sys->sync)

2025-06-27T10:56:53+00:00

Fix RwLock::try_write documentation for WouldBlock condition

2025-06-26T10:03:43+00:00

Rollup merge of #140715 - lukaslueg:oncecellsyncdocs, r=tgross35

2025-06-03T05:03:42+00:00

Clarify &mut-methods' docs on sync::OnceLock Three small changes to the docs of `sync::OnceLock`: * The docs for `OnceLock::take()` used to [say](https://doc.rust-lang.org/std/sync/struct.OnceLock.html#method.take) "**Safety** is guaranteed by requiring a mutable reference." (emphasis mine). While technically correct, imho its not necessary to even mention safety - as opposed to unsafety - here: Safety never comes up wrt `OnceLock`, as there is (currently) no way to interact with a `OnceLock` in an unsafe way; there are no unsafe methods on `OnceLock`, so there is "safety" guarantee required anywhere. What we simply meant to say is "**Synchronization** is guaranteed...". * I've add that phrase to the other methods of `OnceLock` which take a `&mut self`, to highlight the fact that having a `&mut OnceLock` guarantees that synchronization with other threads is not required. This is the same as with [`Mutex::get_mut()`](https://doc.rust-lang.org/std/sync/struct.Mutex.html#method.get_mut), [`Cell::get_mut()`](https://doc.rust-lang.org/std/cell/struct.Cell.html#method.get_mut), and others. * In that spirit, the half-sentence "or being initialized" was removed from `get_mut()`, as there is no way that the `OnceLock` is being initialized while we are holding `&mut` to it. Probably a copy&paste from `.get()`

Clarify &mut-methods' docs on sync::OnceLock

2025-05-28T16:31:28+00:00

Rollup merge of #140369 - jplatte:mutex-rwlock-data-ptr, r=Amanieu

2025-05-28T14:28:07+00:00

Add data_ptr method to Mutex and RwLock Implementation of https://github.com/rust-lang/rust/issues/140368 / https://github.com/rust-lang/libs-team/issues/531. I tried to write a useful safety section about when it is safe to read or write through the returned pointers, but couldn't come up with something nice. Hoping this PR is still useful without that. I'm happy to add any doc strings other people come up with if needed before merge, of course. Unresolved questions: - Return a `LockResult` or not? - Return `*mut T` like existing APIs (`Cell::as_ptr` / `MaybeUninit::as[_mut]_ptr` / `Vec::as_ptr` / ...) or be more precise and return `NonNull`?