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

Age	Commit message (Collapse)	Author	Lines
2021-10-03	Practice diagnostic message convention	Hirochika Matsumoto	-1/+1

2021-10-02	Make diangostic item names consistent	Cameron Steffen	-1/+1

2021-09-28	ref/refmut	Gus Wynn	-1/+1

2021-09-27	lock types	Gus Wynn	-0/+6

2021-07-01	Move Mutex::unlock to T: ?Sized	Mark Mansi	-20/+20

2021-05-24	minor rewording after review	Taylor Yu	-2/+2
	Use "the `WouldBlock` error" instead of "the error `WouldBlock`", etc.
2021-05-20	doc: clarify Mutex::try_lock, etc. errors	Taylor Yu	-2/+8
	Clarify error returns from Mutex::try_lock, RwLock::try_read, RwLock::try_write to make it more obvious that both poisoning and the lock being already locked are possible errors.
2021-04-28	Simplify `Mutex::into_inner`	Benoît du Garreau	-19/+2

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

2021-03-27	Improve Debug implementations of Mutex and RwLock.	Mara Bos	-4/+8
	They now show the poison flag and use debug_non_exhaustive.
2021-02-18	add Mutex::unlock	mark	-0/+20

2020-10-07	(docs): make mutex error comment consistent with codebase	Steve Manuel	-1/+1

2020-09-27	Split sys_common::Mutex in StaticMutex and MovableMutex.	Mara Bos	-26/+4
	The (unsafe) Mutex from sys_common had a rather complicated interface. You were supposed to call init() manually, unless you could guarantee it was neither moved nor used reentrantly. Calling `destroy()` was also optional, although it was unclear if 1) resources might be leaked or not, and 2) if destroy() should only be called when `init()` was called. This allowed for a number of interesting (confusing?) different ways to use this Mutex, all captured in a single type. In practice, this type was only ever used in two ways: 1. As a static variable. In this case, neither init() nor destroy() are called. The variable is never moved, and it is never used reentrantly. It is only ever locked using the LockGuard, never with raw_lock. 2. As a Boxed variable. In this case, both init() and destroy() are called, it will be moved and possibly used reentrantly. No other combinations are used anywhere in `std`. This change simplifies things by splitting this Mutex type into two types matching the two use cases: StaticMutex and MovableMutex. The interface of both new types is now both safer and simpler. The first one does not call nor expose init/destroy, and the second one calls those automatically in its new() and Drop functions. Also, the locking functions of MovableMutex are no longer unsafe.
2020-09-20	Replace unneeded `unsafe` calls to `.get()` with calls to `.get_mut()`	Daniel Henry-Mantilla	-3/+1

2020-09-06	Auto merge of #76128 - poliorcetics:doc-use-arc-clone, r=KodrAus	bors	-4/+4
	Use Arc::clone and Rc::clone in documentation This PR replaces uses of `x.clone()` by `Rc::clone(&x)` (or `Arc::clone(&x)`) to better match the documentation for those types. @rustbot modify labels: T-doc
2020-08-31	std: move "mod tests/benches" to separate files	Lzu Tao	-242/+3
	Also doing fmt inplace as requested.
2020-08-30	Move to Arc::clone(&x) over x.clone() in library/std	Alexis Bourget	-4/+4

2020-08-22	Use intra-doc-links in `std::sync::*`	LeSeulArtichaut	-16/+8

2020-07-27	mv std libs to library/	mark	-0/+767