rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2025-07-15	Update poison.rs	Martin Ombura Jr.	-1/+1
	Typo in word "below"
2025-06-27	Update poison.rs to fix the typo (sys->sync)	Kurt Heiritz (pseudo)	-1/+1

2025-04-27	use generic Atomic type where possible	Christopher Durham	-2/+2
	in core/alloc/std only for now, and ignoring test files Co-authored-by: Pavel Grigorenko <GrigorenkoPV@ya.ru>
2025-01-02	Move some things to `std::sync::poison` and reexport them in `std::sync`	Pavel Grigorenko	-3/+84

2024-11-30	Add value accessor methods to `Mutex` and `RwLock`	EFanZh	-17/+18

2024-07-29	Reformat `use` declarations.	Nicholas Nethercote	-1/+0
	The previous commit updated `rustfmt.toml` appropriately. This commit is the outcome of running `x fmt --all` with the new formatting options.
2024-07-26	Fix doc nits	John Arundel	-2/+2
	Many tiny changes to stdlib doc comments to make them consistent (for example "Returns foo", rather than "Return foo", per RFC1574), adding missing periods, paragraph breaks, backticks for monospace style, and other minor nits. https://github.com/rust-lang/rfcs/blob/master/text/1574-more-api-documentation-conventions.md#appendix-a-full-conventions-text
2024-03-12	Use `min_exhaustive_patterns` in core & std	Nadrieril	-0/+8

2024-02-25	Auto merge of #117107 - zachs18:mapped-mutex-guard, r=Amanieu	bors	-0/+1
	Implement `MappedMutexGuard`, `MappedRwLockReadGuard`, and `MappedRwLockWriteGuard`. ACP: https://github.com/rust-lang/libs-team/issues/260 Tracking issue: https://github.com/rust-lang/rust/issues/117108 <details> <summary> (Outdated) </summary> `MutexState`/`RwLockState` structs ~~Having `sys::(Mutex\|RwLock)` and `poison::Flag` as separate fields in the `Mutex`/`RwLock` would require `MappedMutexGuard`/`MappedRwLockWriteGuard` to hold an additional pointer, so I combined the two fields into a `MutexState`/`RwLockState` struct. This should not noticeably affect perf or layout, but requires an additional field projection when accessing the former `.inner` or `.poison` fields (now `.state.inner` and `.state.poison`).~~ If this is not desired, then `MappedMutexGuard`/`MappedRwLockWriteGuard` can instead hold separate pointers to the two fields. </details> The doc-comments are mostly copied from the existing `Guard` doc-comments, with some parts from `lock_api::MappedGuard`'s doc-comments. Unresolved question: Are more tests needed?
2023-12-05	Allow cloning `poison::Guard`s.	Zachary S	-0/+1
	(makes implementing `Mapped*Guard` easier)
2022-08-15	Optimize poison guards to ZSTs when panic=abort	Tyler Mandry	-2/+49

2022-06-19	Auto merge of #97791 - m-ou-se:const-locks, r=m-ou-se	bors	-0/+1
	Make {Mutex, Condvar, RwLock}::new() const. This makes it possible to have `static M: Mutex<_> = Mutex::new(..);` 🎉 Our implementations [on Linux](https://github.com/rust-lang/rust/pull/95035), [on Windows](https://github.com/rust-lang/rust/pull/77380), and various BSDs and some tier 3 platforms have already been using a non-allocating const-constructible implementation. As of https://github.com/rust-lang/rust/pull/97647, the remaining platforms (most notably macOS) now have a const-constructible implementation as well. This means we can finally make these functions publicly const. Tracking issue: https://github.com/rust-lang/rust/issues/93740
2022-06-09	Avoid `thread::panicking()` in non-poisoning methods of `Mutex` and `RwLock`	Josh Stone	-1/+8
	`Mutex::lock()` and `RwLock::write()` are poison-guarded against panics, in that they set the poison flag if a panic occurs while they're locked. But if we're already in a panic (`thread::panicking()`), they leave the poison flag alone. That check is a bit of a waste for methods that never set the poison flag though, namely `get_mut()`, `into_inner()`, and `RwLock::read()`. These use-cases are now split to avoid that unnecessary call.
2022-06-06	Make all {Mutex, Condvar, RwLock}::new #[inline].	Mara Bos	-0/+1

2022-04-26	Add functions to un-poison Mutex and RwLock	Thayne McCombs	-0/+5
	See discussion at https://internals.rust-lang.org/t/unpoisoning-a-mutex/16521/3
2022-03-10	Use implicit capture syntax in format_args	T-O-R-U-S	-1/+1
	This updates the standard library's documentation to use the new syntax. The documentation is worthwhile to update as it should be more idiomatic (particularly for features like this, which are nice for users to get acquainted with). The general codebase is likely more hassle than benefit to update: it'll hurt git blame, and generally updates can be done by folks updating the code if (and when) that makes things more readable with the new format. A few places in the compiler and library code are updated (mostly just due to already having been done when this commit was first authored).
2021-07-29	Fix may not to appropriate might not or must not	Ali Malik	-1/+1

2021-04-22	Move `sys_common::poison` to `sync::poison`	Christiaan Dirkx	-0/+259