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

Age	Commit message (Collapse)	Author	Lines
2023-01-11	Move /src/test to /tests	Albert Larsan	-29/+0

2020-04-11	rustc: Add a warning count upon completion	RoccoDev	-0/+2

2020-03-23	Reword unused variable warning	Alex Tokarev	-1/+1

2020-01-24	Normalise notes with the/is	varkor	-1/+1

2019-07-17	normalize use of backticks in compiler messages for librustc/lint	Samy Kacimi	-2/+2
	https://github.com/rust-lang/rust/issues/60532
2019-03-11	Update tests	Vadim Petrochenkov	-3/+3

2019-01-28	Unused variable suggestions on all patterns.	David Wood	-1/+1
	This commit extends existing suggestions to prefix unused variable bindings in match arms with an underscore so that it applies to all patterns in a match arm.
2019-01-08	improve non_snake_case diagnostics	Andy Russell	-4/+4
	Use a structured suggestion and tighten the span to just the identifier.
2018-12-25	Remove licenses	Mark Rousskov	-4/+4

2018-11-07	Removed `#[rustc_error]` from tests that are all `// compile-pass`.	Felix S. Klock II	-13/+0
	I also added `// skip-codegen` to each one, to address potential concerns that this change would otherwise slow down our test suite spending time generating code for files that are really just meant to be checks of compiler diagnostics. (However, I will say: My preference is to not use `// skip-codegen` if one can avoid it. We can use all the testing of how we drive LLVM that we can get...) (Updated post rebase.)
2018-03-16	Update tests	John Kåre Alsaker	-0/+2

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

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

2018-01-31	concerning well-formed suggestions for unused shorthand field patterns	Zack M. Davis	-2/+1
	Previously, unused variables would get a note that the warning could be silenced by prefixing the variable with an underscore, but that doesn't work for field shorthand patterns, which the liveness analysis didn't know about. The "to avoid this warning" verbiage seemed unnecessary. Resolves #47390.
2017-11-24	Merge cfail and ui tests into ui tests	Oliver Schneider	-8/+9

2017-09-14	"avoid" is a better word here than "disable"	est31	-1/+1

2017-08-16	Add a note to unused variables	Guillaume Gomez	-0/+1

2017-08-09	rustc: Rearchitect lints to be emitted more eagerly	Alex Crichton	-23/+26
	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	-1/+1
	This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e.
2017-06-26	make lint on-by-default/implied-by messages appear only once	Zack M. Davis	-4/+2
	From review discussion on #38103 (https://github.com/rust-lang/rust/pull/38103#discussion_r94845060).
2017-05-24	Change error count messages	Michael Kohl	-1/+1
	See #33525 for details.
2017-02-04	note wording: lint implied by lint group, not lint group implies lint	Zack M. Davis	-3/+3

2017-02-04	note individual lint name set via lint group attribute in notes	Zack M. Davis	-0/+4
	Warning or error messages set via a lint group attribute (e.g. `#[deny(warnings)]`) should still make it clear which individual lint (by name) was triggered, similarly to how we include "on by default" language for default lints. This—and, while we're here, the existing "on by default" language—can be tucked into a note rather than cluttering the main error message. This occasions the slightest of refactorings (we now have to get the diagnostic-builder with the main message first, before matching on the lint source). This is in the matter of #36846.
2017-01-06	Fix test/ui/span/issue-24690.stderr	comex	-12/+12
	The errors are now emitted in a different order (in order of source location rather than going back and forth) but otherwise everything's the same.
2016-10-26	deduplicate one-time diagnostics on lint ID as well as span and message	Zack M. Davis	-0/+32
	Some lint-level attributes (like `bad-style`, or, more dramatically, `warnings`) can affect more than one lint; it seems fairer to point out the attribute once for each distinct lint affected. Also, a UI test is added. This remains in the matter of #24690.