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

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

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

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

2021-09-11	Rollup merge of #88757 - andrewhickman:master, r=jackh726	Jubilee	-0/+5
	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	-0/+5
	Fixes #88701
2021-09-04	Use verbose suggestions and only match if the + is seen before a numeric literal	Theodore Luo Wang	-2/+2

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

2021-06-20	Update rustfix for compiletest.	Eric Huss	-0/+1

2020-07-22	Correctly parse `{} && false` in tail expression	Esteban Küber	-6/+0
	Fix #74233.
2019-04-30	Reword ambigous parse error to fit with the current error	Esteban Küber	-2/+2

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

2019-04-29	Identify when a stmt could have been parsed as an expr	Esteban Küber	-0/+34
	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.