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

Age	Commit message (Collapse)	Author	Lines
2014-10-07	Put slicing syntax behind a feature gate.	Nick Cameron	-1/+1
	[breaking-change] If you are using slicing syntax you will need to add #![feature(slicing_syntax)] to your crate.
2014-10-02	Revert "Put slicing syntax behind a feature gate."	Aaron Turon	-1/+1
	This reverts commit 95cfc35607ccf5f02f02de56a35a9ef50fa23a82.
2014-10-02	Put slicing syntax behind a feature gate.	Nick Cameron	-1/+1
	[breaking-change] If you are using slicing syntax you will need to add #![feature(slicing_syntax)] to your crate.
2014-08-19	Add a test for the fix of issue 16589	nham	-0/+1

2014-08-13	core: Add binary_search and binary_search_elem methods to slices.	Brian Anderson	-0/+1
	These are like the existing bsearch methods but if the search fails, it returns the next insertion point. The new `binary_search` returns a `BinarySearchResult` that is either `Found` or `NotFound`. For convenience, the `found` and `not_found` methods convert to `Option`, ala `Result`. Deprecate bsearch and bsearch_elem.
2014-08-04	stabilize atomics (now atomic)	Aaron Turon	-1/+1
	This commit stabilizes the `std::sync::atomics` module, renaming it to `std::sync::atomic` to match library precedent elsewhere, and tightening up behavior around incorrect memory ordering annotations. The vast majority of the module is now `stable`. However, the `AtomicOption` type has been deprecated, since it is essentially unused and is not truly a primitive atomic type. It will eventually be replaced by a higher-level abstraction like MVars. Due to deprecations, this is a: [breaking-change]
2014-06-29	Extract tests from libcore to a separate crate	Steven Fackler	-0/+31
	Libcore's test infrastructure is complicated by the fact that many lang items are defined in the crate. The current approach (realcore/realstd imports) is hacky and hard to work with (tests inside of core::cmp haven't been run for months!). Moving tests to a separate crate does mean that they can only test the public API of libcore, but I don't feel that that is too much of an issue. The only tests that I had to get rid of were some checking the various numeric formatters, but those are also exercised through normal format! calls in other tests.