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

Age	Commit message (Collapse)	Author	Lines
2018-03-14	update tests	Guillaume Gomez	-1/+1

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

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

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

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

2017-11-12	Improve SubSupConflict case with one named, one anonymous lifetime parameter ↵	Cengiz Can	-29/+5
	#42701
2017-07-02	Revert "Change error count messages"	Ariel Ben-Yehuda	-1/+1
	This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e.
2017-05-24	Change error count messages	Michael Kohl	-1/+1
	See #33525 for details.
2017-05-18	Fix off-by-one error in column number in `explain_span`.	Florian Hartwig	-2/+2

2017-05-13	rustc: use DefId instead of CodeExtent for FreeRegion's scope.	Eduard-Mihai Burtescu	-8/+6

2017-04-20	Reduce visual clutter of multiline start when possible	Esteban Küber	-4/+4
	When a span starts on a line with nothing but whitespace to the left, and there are no other annotations in that line, simplify the visual representation of the span. Go from: ```rust error[E0072]: recursive type `A` has infinite size --> file2.rs:1:1 \| 1 \| struct A { \| _^ starting here... 2 \| \| a: A, 3 \| \| } \| \|_^ ...ending here: recursive type has infinite size \| ``` To: ```rust error[E0072]: recursive type `A` has infinite size --> file2.rs:1:1 \| 1 \| / struct A { 2 \| \| a: A, 3 \| \| } \| \|_^ recursive type has infinite size ``` Remove `starting here...`/`...ending here` labels from all multiline diagnostics.
2017-04-11	Highlight and simplify mismatched types	Esteban Küber	-1/+1
	Shorten mismatched types errors by replacing subtypes that are not different with `_`, and highlighting only the subtypes that are different. Given a file ```rust struct X<T1, T2> { x: T1, y: T2, } fn foo() -> X<X<String, String>, String> { X { x: X {x: "".to_string(), y: 2}, y: "".to_string()} } fn bar() -> Option<String> { "".to_string() } ``` provide the following output ```rust error[E0308]: mismatched types --> file.rs:6:5 \| 6 \| X { x: X {x: "".to_string(), y: 2}, y: "".to_string()} \| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `std::string::String`, found {integer} \| = note: expected type `X<X<_, std::string::String>, _>` ^^^^^^^^^^^^^^^^^^^ // < highlighted found type `X<X<_, {integer}>, _>` ^^^^^^^^^ // < highlighted error[E0308]: mismatched types --> file.rs:6:5 \| 10 \| "".to_string() \| ^^^^^^^^^^^^^^ expected struct `std::option::Option`, found `std::string::String` \| = note: expected type `Option<std::string::String>` ^^^^^^^ ^ // < highlighted found type `std::string::String` ```
2017-02-17	remove vestiges of the old suggestion machinery	Niko Matsakis	-0/+29

2017-02-17	add some sample UI error test cases	Niko Matsakis	-0/+8
	These are some samples that I have been focusing on improving over time. In this PR, I mainly want to stem the bleeding where we in some cases we show an error that gives you no possible way to divine the problem.