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

Age	Commit message (Collapse)	Author	Lines
2015-09-20	Miscellaneous cleanup for old issues.	Lee Jeffery	-12/+11

2015-05-29	Add map and filter_map associated functions to std::cell::Ref and RefMut	Simon Sapin	-0/+76
	See design discussion in https://github.com/rust-lang/rust/pull/25747
2015-05-28	Move std::cell::clone_ref to a clone associated function on std::cell::Ref	Simon Sapin	-2/+2
	... and generalize the bounds on the value type.
2015-05-13	Rebasing	Nick Cameron	-11/+12

2015-05-02	Make `UnsafeCell`, `RefCell`, `Mutex`, and `RwLock` accept DSTs	P1start	-0/+24
	This + DST coercions (#24619) would allow code like `Rc<RefCell<Box<Trait>>>` to be simplified to `Rc<RefCell<Trait>>`.
2015-03-31	std: Clean out #[deprecated] APIs	Alex Crichton	-8/+5
	This commit cleans out a large amount of deprecated APIs from the standard library and some of the facade crates as well, updating all users in the compiler and in tests as it goes along.
2015-03-26	Mass rename uint/int to usize/isize	Alex Crichton	-4/+4
	Now that support has been removed, all lingering use cases are renamed.
2015-03-09	Rename #[should_fail] to #[should_panic]	Steven Fackler	-1/+1

2015-02-10	Deprecating i/u suffixes in libcoretest	Alfie John	-12/+12

2015-02-01	std: Deprecate RefCell::{try_borrow, try_borrow_mut}	Alex Crichton	-0/+4
	The existence of these two functions is at odds with our current [error conventions][conventions] which recommend that panicking and `Result`-like variants should not be provided together. [conventions]: https://github.com/rust-lang/rfcs/blob/master/text/0236-error-conventions.md#do-not-provide-both-result-and-fail-variants This commit adds a new `borrow_state` function returning a `BorrowState` enum to `RefCell` which serves as a replacemnt for the `try_borrow` and `try_borrow_mut` functions.
2015-01-30	Remove all `i` suffixes	Tobias Bucher	-11/+11

2015-01-21	Minor fixes	Brian Anderson	-1/+0

2015-01-08	Improvements to feature staging	Brian Anderson	-1/+1
	This gets rid of the 'experimental' level, removes the non-staged_api case (i.e. stability levels for out-of-tree crates), and lets the staged_api attributes use 'unstable' and 'deprecated' lints. This makes the transition period to the full feature staging design a bit nicer.
2015-01-06	core: split into fmt::Show and fmt::String	Sean McArthur	-4/+4
	fmt::Show is for debugging, and can and should be implemented for all public types. This trait is used with `{:?}` syntax. There still exists #[derive(Show)]. fmt::String is for types that faithfully be represented as a String. Because of this, there is no way to derive fmt::String, all implementations must be purposeful. It is used by the default format syntax, `{}`. This will break most instances of `{}`, since that now requires the type to impl fmt::String. In most cases, replacing `{}` with `{:?}` is the correct fix. Types that were being printed specifically for users should receive a fmt::String implementation to fix this. Part of #20013 [breaking-change]
2014-12-06	libcoretest: remove unnecessary `as_slice()` calls	Jorge Aparicio	-4/+4

2014-11-14	impl Default for Cell and RefCell	Stepan Koltsov	-0/+13
	It is necessary to have #[deriving(Default)] for struct containing cells like Cell<u32>.
2014-10-24	Add as_unsafe_cell() for Cell and RefCell	Keegan McAllister	-0/+19
	Fixes #18131.
2014-06-29	Extract tests from libcore to a separate crate	Steven Fackler	-0/+129
	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.