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

Age	Commit message (Collapse)	Author	Lines
2023-01-10	add `SyncSender::send_timeout` test	Ibraheem Ahmed	-0/+9

2022-12-04	remove no-op 'let _ = '	Ralf Jung	-9/+3

2022-11-09	remove mention of rust-lang#39364 from mpsc docs	Ibraheem Ahmed	-28/+0

2022-11-09	implement `sync::mpsc` as a wrapper around `sync::mpmc`	Ibraheem Ahmed	-406/+24

2022-03-10	Use implicit capture syntax in format_args	T-O-R-U-S	-10/+10
	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).
2022-01-03	Make `Receiver::into_iter` into a clickable link	zohnannor	-1/+2
	The documentation on `std::sync::mpsc::Iter` and `std::sync::mpsc::TryIter` provides links to the corresponding `Receiver` methods, unlike `std::sync::mpsc::IntoIter` does. This was left out in c59b188aaeadea32625534250d1f5120420be000 Related to #29377
2021-10-30	Add #[must_use] to remaining std functions (O-Z)	John Kugelman	-0/+2

2021-06-15	Rollup merge of #80269 - pickfire:patch-4, r=joshtriplett	Yuki Okushi	-7/+46
	Explain non-dropped sender recv in docs Original senders that are still hanging around could cause Receiver::recv to not block since this is a potential footgun for beginners, clarify more on this in the docs for readers to be aware about it. Maybe it would be better to show an example of the pattern where `drop(tx)` is used when it is being cloned multiple times? Although I have seen it in quite a few articles but I am surprised that this part is not very clear with the current words without careful reading. > If the corresponding Sender has disconnected, or it disconnects while this call is blocking, this call will wake up and return Err to indicate that no more messages can ever be received on this channel. However, since channels are buffered, messages sent before the disconnect will still be properly received. Some words there may seemed similar if I carefully read and relate it but if I am new, I probably does not know "drop" makes it "disconnected". So I mention the words "drop" and "alive" to make it more relatable to lifetime.
2021-06-12	Explain non-dropped sender recv in docs	Ivan Tham	-7/+46
	Original senders that are still hanging around could cause Receiver::recv to not block since this is a potential footgun for beginners, clarify more on this in the docs for readers to be aware about it. Fix minor tidbits in sender recv doc Co-authored-by: Dylan DPC <dylan.dpc@gmail.com> Add example for unbounded receive loops in doc Show the drop(tx) pattern, based on tokio docs https://tokio-rs.github.io/tokio/doc/tokio/sync/index.html Fix example code for drop sender recv Fix wording in sender docs Co-authored-by: Josh Triplett <josh@joshtriplett.org>
2021-04-21	Replace all `fmt.pad` with `debug_struct`	Christiaan Dirkx	-1/+1

2021-03-27	Use DebugStruct::finish_non_exhaustive() in std.	Mara Bos	-3/+3

2021-03-01	Add diagnostic items	Cameron Steffen	-0/+1

2020-11-07	Convert a bunch of intra-doc links	Camelid	-3/+0

2020-09-21	Applied review comments	Erik Hofmayer	-0/+6

2020-09-20	Documented From impls in std/sync/mpsc/mod.rs	Erik Hofmayer	-0/+9

2020-08-31	std: move "mod tests/benches" to separate files	Lzu Tao	-1361/+6
	Also doing fmt inplace as requested.
2020-08-22	Use intra-doc-links in `std::sync::*`	LeSeulArtichaut	-86/+22

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