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

Age	Commit message (Collapse)	Author	Lines
2018-04-19	Tweak some stabilizations in libstd	Alex Crichton	-2/+2
	This commit tweaks a few stable APIs in the `beta` branch before they hit stable. The `str::is_whitespace` and `str::is_alphanumeric` functions were deleted (added in #49381, issue at #49657). The `and_modify` APIs added in #44734 were altered to take a `FnOnce` closure rather than a `FnMut` closure. Closes #49581 Closes #49657
2018-04-16	Auto merge of #48945 - clarcharr:iter_exhaust, r=Kimundi	bors	-2/+1
	Replace manual iterator exhaust with for_each(drop) This originally added a dedicated method, `Iterator::exhaust`, and has since been replaced with `for_each(drop)`, which is more idiomatic. <del>This is just shorthand for `for _ in &mut self {}` or `while let Some(_) = self.next() {}`. This states the intent a lot more clearly than the identical code: run the iterator to completion. <del>At least personally, my eyes tend to gloss over `for _ in &mut self {}` without fully paying attention to what it does; having a `Drop` implementation akin to: <del>`for _ in &mut self {}; unsafe { free(self.ptr); }`</del> <del>Is not as clear as: <del>`self.exhaust(); unsafe { free(self.ptr); }` <del>Additionally, I've seen debate over whether `while let Some(_) = self.next() {}` or `for _ in &mut self {}` is more clear, whereas `self.exhaust()` is clearer than both.
2018-04-04	Replace manual iter exhaust with for_each(drop).	Clar Charr	-2/+1

2018-03-29	Move RangeArguments to {core::std}::ops and rename to RangeBounds	Simon Sapin	-4/+4
	These unstable items are deprecated: * The `std::collections::range::RangeArgument` reexport * The `std::collections::range` module.
2018-03-29	Move alloc::Bound to {core,std}::ops	Simon Sapin	-2/+2
	The stable reexport `std::collections::Bound` is now deprecated. Another deprecated reexport could be added in `alloc`, but that crate is unstable.
2018-03-25	Implement get_key_value for HashMap, BTreeMap	Diggory Blake	-0/+27

2018-03-03	core: Update stability attributes for FusedIterator	Ulrik Sverdrup	-8/+8

2018-03-03	core: Stabilize FusedIterator	Ulrik Sverdrup	-8/+8
	FusedIterator is a marker trait that promises that the implementing iterator continues to return `None` from `.next()` once it has returned `None` once (and/or `.next_back()`, if implemented). The effects of FusedIterator are already widely available through `.fuse()`, but with stable `FusedIterator`, stable Rust users can implement this trait for their iterators when appropriate.
2018-02-25	1.25.0 -> 1.26.-	Manish Goregaokar	-1/+1

2018-02-12	Stabilize 'entry_and_modify' feature for BTreeMap	hedgehog1024	-2/+1

2018-01-28	Document that `Index` ops can panic on `HashMap` & `BTreeMap`.	Corey Farwell	-0/+5
	Fixes https://github.com/rust-lang/rust/issues/47011.
2017-10-06	Implement `entry_and_modify`	mchlrhw	-0/+34

2017-09-05	Avoid weird or_insert_with example	Jon Gjengset	-3/+1

2017-09-05	Add or_default to Entry APIs	Jon Gjengset	-0/+29

2017-08-15	use field init shorthand EVERYWHERE	Zack M. Davis	-7/+7
	Like #43008 (f668999), but _much more aggressive_.
2017-06-30	Revert "Stabilize RangeArgument"	Steven Fackler	-2/+3
	This reverts commit 143206d54d7558c2326212df99efc98110904fdb.
2017-06-24	Stabilize RangeArgument	Steven Fackler	-3/+2
	Move it and Bound to core::ops while we're at it. Closes #30877
2017-06-23	Relax Debug constraints when debugging {HashMap,BTreeMap}::{Keys,Values}.	Federico Ravasio	-2/+2
	Fixed #41924.
2017-06-23	Correctly iterate on keys/values when debugging BTreeMap::{Keys,Values}.	Federico Ravasio	-2/+2

2017-06-13	Merge crate `collections` into `alloc`	Murarth	-0/+2460