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

Age	Commit message (Collapse)	Author	Lines
2019-03-11	Update tests	Vadim Petrochenkov	-24/+24

2018-12-25	Remove licenses	Mark Rousskov	-259/+54

2018-10-16	Remove outdated test	varkor	-19/+6

2018-07-23	Match errors using the callsite of macro expansions	Federico Poli	-5/+16

2018-05-16	Remove empty files	Jane Lusby	-0/+0

2018-05-11	unary op filter, dereference hint	Roman Stoliar	-3/+1

2018-05-11	added missing implementation hint	Roman Stoliar	-0/+2

2018-04-20	Revert stabilization of `feature(never_type)`.	Felix S. Klock II	-7/+7
	This commit is just covering the feature gate itself and the tests that made direct use of `!` and thus need to opt back into the feature. A follow on commit brings back the other change that motivates the revert: Namely, going back to the old rules for falling back to `()`.
2018-04-13	Rename must-compile-successfully into compile-pass	Guillaume Gomez	-2/+2

2018-03-14	Fix ui test errors	Andrew Cann	-1/+1

2018-03-14	Make coerce_never lint an error	Andrew Cann	-28/+11
	Remove the coerce_never lint and make the behaviour an error.
2018-03-14	stabilise feature(never_type)	Andrew Cann	-54/+37
	Replace feature(never_type) with feature(exhaustive_patterns). feature(exhaustive_patterns) only covers the pattern-exhaustives checks that used to be covered by feature(never_type)
2018-03-14	update tests	Guillaume Gomez	-1/+1

2018-02-26	Update UI tests	Vadim Petrochenkov	-57/+57

2018-02-25	Update ui tests	Guillaume Gomez	-0/+1

2017-12-10	Add must-compile-successfully comment to appropriate ui tests.	Tommy Ip	-0/+4

2017-11-30	make coercions to `!` in unreachable code a hard error	Ariel Ben-Yehuda	-6/+23
	This was added to cover up a lazy extra semicolon in #35849, but does not actually make sense. This is removed as a part of the stabilization of `never_type`.
2017-11-26	mention nightly in -Z external-macro-backtrace note	Alex Burka	-11/+11

2017-11-24	Merge cfail and ui tests into ui tests	Oliver Schneider	-49/+50

2017-11-20	address review comments	Alex Burka	-11/+11

2017-11-19	use -Z flag instead of env var	Alex Burka	-11/+11

2017-11-19	update UI tests	Alex Burka	-11/+11

2017-08-09	rustc: Rearchitect lints to be emitted more eagerly	Alex Crichton	-1/+13
	In preparation for incremental compilation this commit refactors the lint handling infrastructure in the compiler to be more "eager" and overall more incremental-friendly. Many passes of the compiler can emit lints at various points but before this commit all lints were buffered in a table to be emitted at the very end of compilation. This commit changes these lints to be emitted immediately during compilation using pre-calculated lint level-related data structures. Linting today is split into two phases, one set of "early" lints run on the `syntax::ast` and a "late" set of lints run on the HIR. This commit moves the "early" lints to running as late as possible in compilation, just before HIR lowering. This notably means that we're catching resolve-related lints just before HIR lowering. The early linting remains a pass very similar to how it was before, maintaining context of the current lint level as it walks the tree. Post-HIR, however, linting is structured as a method on the `TyCtxt` which transitively executes a query to calculate lint levels. Each request to lint on a `TyCtxt` will query the entire crate's 'lint level data structure' and then go from there about whether the lint should be emitted or not. The query depends on the entire HIR crate but should be very quick to calculate (just a quick walk of the HIR) and the red-green system should notice that the lint level data structure rarely changes, and should hopefully preserve incrementality. Overall this resulted in a pretty big change to the test suite now that lints are emitted much earlier in compilation (on-demand vs only at the end). This in turn necessitated the addition of many `#![allow(warnings)]` directives throughout the compile-fail test suite and a number of updates to the UI test suite.
2017-07-02	Revert "Change error count messages"	Ariel Ben-Yehuda	-19/+19
	This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e.
2017-05-27	Add invalid unary operator usage error code	Guillaume Gomez	-1/+1

2017-05-24	Change error count messages	Michael Kohl	-19/+19
	See #33525 for details.
2017-03-30	cherry-pick over the tests I wrote for the reachability code	Niko Matsakis	-0/+1023
	For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.