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

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

2022-12-03	suggest parenthesis around ExprWithBlock BinOp ExprWithBlock	Lukas Markeffsky	-1/+42

2022-10-05	Suggest `.into()` when all other coercion suggestions fail	Michael Goulet	-9/+0

2022-07-07	Shorten span for closures.	Camille GILLOT	-1/+1

2022-06-21	Improve suggestion for calling closure on type mismatch	Michael Goulet	-0/+4

2022-06-16	diagnostics: fix trailing space	klensy	-1/+1

2022-02-27	Make deref suggestion better	Michael Goulet	-0/+5

2022-02-24	diagnostic: suggest parens when users want logical ops, but get closures	Michael Howell	-1/+81

2021-09-11	Rollup merge of #88757 - andrewhickman:master, r=jackh726	Jubilee	-2/+24
	Suggest wapping expr in parentheses on invalid unary negation Fixes #88701
2021-09-06	Suggest wapping expr in parentheses on invalid unary negation	Andrew Hickman	-2/+24
	Fixes #88701
2021-09-04	Use verbose suggestions and only match if the + is seen before a numeric literal	Theodore Luo Wang	-4/+4

2021-09-01	Add checks for a block before a unary plus. Fix failing tests	Theodore Luo Wang	-6/+6

2021-08-11	Modify structured suggestion output	Esteban Küber	-10/+10
	* On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-07-30	Use multispan suggestions more often	Esteban Küber	-12/+24
	* Use more accurate span for `async move` suggestion * Use more accurate span for deref suggestion * Use `multipart_suggestion` more often
2021-06-20	Update rustfix for compiletest.	Eric Huss	-9/+9

2021-02-21	Suggest `return`ing tail expressions that match return type	Esteban Küber	-0/+20
	Some newcomers are confused by the behavior of tail expressions, interpreting that "leaving out the `;` makes it the return value". To help them go in the right direction, suggest using `return` instead when applicable.
2020-07-22	Correctly parse `{} && false` in tail expression	Esteban Küber	-10/+2
	Fix #74233.
2019-11-18	Surround types with backticks in type errors	Esteban Küber	-4/+4

2019-11-18	Remove E0308 note when primary label has all info	Esteban Küber	-12/+0

2019-11-18	review comments: tweak prefix strings	Esteban Küber	-8/+8

2019-10-24	Increase spacing for suggestions in diagnostics	Esteban Küber	-0/+1
	Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-05-02	fix typo	Esteban Küber	-6/+6

2019-04-30	Reword ambigous parse error to fit with the current error	Esteban Küber	-4/+4

2019-04-29	Add test case for #47287	Esteban Küber	-1/+13

2019-04-29	Identify when a stmt could have been parsed as an expr	Esteban Küber	-0/+80
	There are some expressions that can be parsed as a statement without a trailing semicolon depending on the context, which can lead to confusing errors due to the same looking code being accepted in some places and not others. Identify these cases and suggest enclosing in parenthesis making the parse non-ambiguous without changing the accepted grammar.