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

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

2022-10-05	Delay function resolution error until typeck	Michael Goulet	-11/+11

2022-06-16	fix one more case of trailing space	klensy	-1/+1

2021-08-11	Modify structured suggestion output	Esteban Küber	-5/+5
	* On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2020-08-10	Add missing primary label	Esteban Küber	-1/+1

2020-08-10	Tweak ordering of suggestions	Esteban Küber	-4/+7
	Modify logic to make it easier to follow and recover labels that would otherwise be lost.
2020-07-14	Suggest struct pat on incorrect unit or tuple pat	Esteban Küber	-6/+9
	When encountering a unit or tuple pattern for a struct-like item, suggest using the correct pattern. Use `insert_field_names_local` when evaluating variants and store field names even when the list is empty in order to produce accurate structured suggestions.
2020-04-26	Tweak some suggestions in `rustc_resolve`	Esteban Küber	-3/+6

2020-03-21	Bless tests	LeSeulArtichaut	-12/+9

2019-10-27	Point at local similarly named element and tweak references to variants	Esteban Küber	-8/+14
	Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method.
2019-10-24	Increase spacing for suggestions in diagnostics	Esteban Küber	-0/+2
	Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-10-13	Bring attention to suggestions when the only difference is capitalization	Esteban Küber	-1/+1

2019-09-22	Point at definition when misusing ADT	Esteban Küber	-0/+3
	When given `struct Foo(usize)` and using it as `Foo {}` or `Foo`, point at `Foo`'s definition in the error.
2019-05-02	fix typo	Esteban Küber	-2/+2

2019-04-19	Emit specific error for struct literal in conditions	Esteban Küber	-39/+15

2019-03-22	Reword type ascription note to reduce verbosity	Esteban Küber	-12/+2

2019-03-22	Review comment	Esteban Küber	-2/+2

2019-03-22	Expand suggestions for type ascription parse errors	Esteban Küber	-0/+26

2019-03-11	Update tests	Vadim Petrochenkov	-1/+1

2019-01-18	Rollup merge of #57725 - estebank:parens, r=michaelwoerister	Mazdak Farrokhzad	-3/+9
	Use structured suggestion to surround struct literal with parenthesis
2019-01-17	Use structured suggestion to surround struct literal with parenthesis	Esteban Küber	-3/+9

2019-01-09	clarify resolve typo suggestion	Andy Russell	-1/+1
	Include the kind of the binding that we're suggesting, and use a structured suggestion.
2018-12-25	Remove licenses	Mark Rousskov	-7/+7

2018-06-04	Suggest braces when a struct literal needs them	Esteban Küber	-2/+41
	When writing a struct literal in an expression that expects a block to be started afterwards (like an `if` statement), do not suggest using the same struct literal: ``` did you mean `S { /* fields * /}`? ``` Instead, suggest surrounding the expression with parentheses: ``` did you mean `(S { /* fields * /})`? ```
2018-03-14	update tests	Guillaume Gomez	-1/+1

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

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

2018-02-08	Move some E0XXX to `ui`	Esteban Küber	-0/+8