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

Age	Commit message (Collapse)	Author	Lines
2018-08-14	Moved compile-fail tests to ui tests.	David Wood	-31/+0

2018-06-23	add `dyn` to display of dynamic (trait) type names	Zack M. Davis	-3/+3
	The `dyn Trait` syntax was stabilized in 199ee327. Resolves #49277.
2017-06-14	suppress trait errors that are implied by other errors	Ariel Ben-Yehuda	-1/+0
	Instead of suppressing only trait errors that are "exact duplicates", display only the "most high-level" error when there are multiple trait errors with the same span that imply each-other. e.g. when there are both `[closure]: Fn` and `[closure]: FnOnce`, omit displaying the `[closure]: FnOnce` bound.
2017-01-30	Merge ty::TyBox into ty::TyAdt	Vadim Petrochenkov	-6/+3

2016-07-31	Don't gate methods `Fn(Mut,Once)::call(mut,once)` with feature ↵	Vadim Petrochenkov	-1/+0
	`unboxed_closures` They are already gated with feature `fn_traits`
2016-05-02	update test cases to reflect new messages	Niko Matsakis	-12/+9

2016-04-05	suggest adding a where-clause when that can help	Ariel Ben-Yehuda	-2/+2
	suggest adding a where-clause when there is an unmet trait-bound that can be satisfied if some type can implement it.
2016-03-30	Fix fallout in tests	Jeffrey Seyfried	-5/+5

2015-03-23	Fallout from changing fn traits to use inheritance rather than bridge	Niko Matsakis	-1/+1
	impls. This is a [breaking-change] (for gated code) in that when you implement `Fn` (`FnMut`) you must also implement `FnOnce`. This commit demonstrates how to fix it.
2015-03-18	Require braces when a closure has an explicit return type. This is a	Niko Matsakis	-1/+1
	[breaking-change]: instead of a closure like `\|\| -> i32 22`, prefer `\|\| -> i32 { 22 }`. Fixes #23420.
2015-02-23	Make traits with by-value-self be considered object safe.	Niko Matsakis	-2/+1

2015-02-04	remove all kind annotations from closures	Jorge Aparicio	-3/+3

2015-01-31	Kill more `isize`s	Tobias Bucher	-1/+1

2015-01-28	Update test files; mostly the problem is that they were using the	Niko Matsakis	-1/+3
	explicit form `Fn<A,B>` and now should use `Fn(A) -> B` or `Fn<A,Output=B>`, but in some cases we get duplicate error reports. This is mildly annoying and arises because of the main error and another error from the projection. Might be worth squashing those, but seems like a separate problem.
2015-01-12	Fix testsuite errors	mdinger	-4/+17

2015-01-08	Update compile-fail tests to use is/us, not i/u.	Huon Wilson	-1/+1

2015-01-07	Test fixes and rebase conflicts	Alex Crichton	-0/+1

2015-01-06	test fallout from isize/usize	Corey Richardson	-8/+8

2014-12-17	Use the sugary syntax to print the `Fn` traits in error messages	P1start	-0/+24