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

Age	Commit message (Collapse)	Author	Lines
2017-06-13	Merge crate `collections` into `alloc`	Murarth	-152/+0

2017-05-21	Make RangeInclusive just a two-field struct	Scott McMurray	-8/+2
	Not being an enum improves ergonomics, especially since NonEmpty could be Empty. It can still be iterable without an extra "done" bit by making the range have !(start <= end), which is even possible without changing the Step trait. Implements RFC 1980
2017-04-10	Apply clippy's doc_markdown improvements to libcollections	Andre Bogus	-1/+1
	Since my last PR led to linker failure, I'm now taking much smaller steps. This only fixes some doc_markdown warnings; as they are in comments only, we shouldn't get any problems building.
2017-03-22	Add 'the' before 'start'/'end'	Stjepan Glavina	-2/+2

2017-03-22	Various fixes to wording consistency in the docs	Stjepan Glavina	-4/+4

2017-03-17	Minor fixups to fix tidy errors	Alex Crichton	-2/+0

2017-02-18	add impl for RangeToInclusive	Djzin	-1/+11

2017-02-18	impl RangeArgument for RangeInclusive and add appropriate tests	Djzin	-1/+17

2017-01-14	make rangeargument methods non-default; simplify impl	djzin	-17/+18

2017-01-14	allow unsized types in `RangeArgument`	djzin	-1/+19

2017-01-14	fix up tests	djzin	-9/+13

2017-01-14	impl RangeArgument for (Bound<T>, Bound<T>)	djzin	-0/+18

2017-01-14	have RangeArgument return a Bound<&T> from each of its methods	djzin	-12/+13

2016-08-24	Remove needless imports in `libcollections`.	Jeffrey Seyfried	-1/+0

2016-08-02	Add doc examples for `range::RangeArgument::{start,end}`.	Corey Farwell	-0/+32

2016-02-27	note work still to be done	Alex Burka	-0/+1
	In particular, uses of inclusive ranges within the standard library are still waiting. Slices and collections can be sliced with `usize` and `Range<usize>`, but not yet `RangeInclusive<usize>`. Also, we need to figure out what to do about `RangeArgument`. Currently it has `start()` and `end()` methods which are pretty much identical to `Range::start` and `Range::end`. For the same reason as Range itself, these methods can't express a range such as `0...255u8` without overflow. The easiest choice, it seems to me, is either changing the meaning of `end()` to be inclusive, or adding a new method, say `last()`, that is inclusive and specifying that `end()` returns `None` in cases where it would overflow. Changing the semantics would be a breaking change, but `RangeArgument` is unstable so maybe we should do it anyway.
2016-01-13	update tracking issue for collections_range	Alex Burka	-2/+3

2015-11-24	rustfmt libcollections	Nick Cameron	-6/+18

2015-08-15	collections: Add issues for unstable features	Alex Crichton	-1/+2

2015-06-17	collections: Split the `collections` feature	Alex Crichton	-0/+1
	This commit also deprecates the `as_string` and `as_slice` free functions in the `string` and `vec` modules.
2015-04-27	collections: Add trait RangeArgument	Ulrik Sverdrup	-0/+45
	RangeArgument is introduced as unstable under the feature(collections_range)