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

Age	Commit message (Collapse)	Author	Lines
2019-09-26	Rename `Expr.node` to `Expr.kind`	varkor	-1/+1
	For both `ast::Expr` and `hir::Expr`.
2019-09-06	reduce visibility	Aleksey Kladov	-1/+1

2019-08-12	Bring back suggestion for splitting `<-` into `< -`	Ilija Tovilo	-0/+2
	Closes #62632
2019-07-30	Unsupport the await!(..) macro.	Mazdak Farrokhzad	-1/+1

2019-06-23	let_chains: Fix bugs in pretty printing.	Mazdak Farrokhzad	-0/+16

2019-06-23	let_chains: Add support for parsing let expressions.	Mazdak Farrokhzad	-4/+3

2019-06-14	Change `...` to `..=` where applicable	Aaron Kutch	-1/+1

2019-06-08	syntax: Move most of the `TokenKind` methods to `Token`	Vadim Petrochenkov	-3/+3

2019-06-06	syntax: Rename `Token` into `TokenKind`	Vadim Petrochenkov	-2/+2

2019-06-06	Always use token kinds through `token` module rather than `Token` type	Vadim Petrochenkov	-25/+25

2019-05-24	Remove `ObsoleteInPlace`	varkor	-10/+4

2019-05-22	Simplify use of keyword symbols	Vadim Petrochenkov	-2/+2

2019-05-09	Rollup merge of #60188 - estebank:recover-block, r=varkor	Mazdak Farrokhzad	-0/+25
	Identify when a stmt could have been parsed as an expr 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. Fix #54186, cc #54482, fix #59975, fix #47287.
2019-05-07	Implement built-in await syntax	Taylor Cramer	-0/+3
	Adds support for .await under the existing async_await feature gate. Moves macro-like await! syntax to the await_macro feature gate. Removes support for `await` as a non-keyword under the `async_await` feature.
2019-05-06	review comments: fix typo and add comments	Esteban Küber	-1/+4

2019-04-29	Identify when a stmt could have been parsed as an expr	Esteban Küber	-0/+22
	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.
2019-02-10	rustc: doc comments	Alexander Regueiro	-2/+2

2019-02-07	libsyntax => 2018	Taiki Endo	-10/+10

2018-12-27	AST/HIR: Introduce `ExprKind::Err` for better error recovery in the front-end	Vadim Petrochenkov	-1/+3

2018-12-25	Remove licenses	Mark Rousskov	-9/+0

2018-12-07	Various minor/cosmetic improvements to code	Alexander Regueiro	-2/+2

2018-08-19	Rename `Catch` variants to `TryBlock`	Scott McMurray	-2/+2
	(Not `Try` since `QuestionMark` is using that.)
2018-07-14	Remove most of `PartialEq` impls from AST and HIR structures	Vadim Petrochenkov	-17/+3

2018-06-21	async await desugaring and tests	Taylor Cramer	-0/+2

2018-05-24	restore emplacement syntax (obsolete)	Niko Matsakis	-5/+11

2018-04-12	AST/HIR: Merge field access expressions for named and numeric fields	Vadim Petrochenkov	-3/+0

2018-04-03	Remove all unstable placement features	Aidan Hobson Sayers	-10/+4
	Closes #22181, #27779
2018-01-15	Move `ExprPrecedence` to `libsyntax/util/parser.rs`	Esteban Küber	-0/+126

2018-01-15	Use single source of truth for expr precedence	Esteban Küber	-61/+1
	Introduce a new unified type that holds the expression precedence for both AST and HIR nodes.
2017-11-06	Using `...` in expressions is now an error	Badel2	-1/+2

2017-09-22	Add support for `..=` syntax	Alex Burka	-8/+9
	Add ..= to the parser Add ..= to libproc_macro Add ..= to ICH Highlight ..= in rustdoc Update impl Debug for RangeInclusive to ..= Replace `...` to `..=` in range docs Make the dotdoteq warning point to the ... Add warning for ... in expressions Updated more tests to the ..= syntax Updated even more tests to the ..= syntax Updated the inclusive_range entry in unstable book
2017-09-07	pprust: increase precedence of block-like exprs	Stuart Pernsteiner	-11/+9

2017-09-06	pprust: fix parenthesization of exprs	Stuart Pernsteiner	-1/+105

2016-11-20	Move `syntax::util::interner` -> `syntax::symbol`, cleanup.	Jeffrey Seyfried	-1/+2

2016-02-27	libsyntax: parse inclusive ranges	Alex Burka	-5/+9

2016-02-11	[breaking-change] don't glob export ast::BinOp_	Oliver Schneider	-40/+40

2015-12-16	Add ExprType to HIR and make everything compile	Vadim Petrochenkov	-7/+9
	+ Apply parser changes manually + Add feature gate
2015-10-27	Fix restrictions when parsing rhs of equalities	Simonas Kazlauskas	-0/+10

2015-10-27	Fix prefix range expressions being not parsed	Simonas Kazlauskas	-0/+9

2015-10-27	Generalise associative operator parsing	Simonas Kazlauskas	-0/+191
	This commit generalises parsing of associative operators from left-associative only (with some ugly hacks to support right-associative assignment) to properly left/right-associative operators. Parsing still is not general enough to handle non-associative, non-highest-precedence prefix or non-highest-precedence postfix operators (e.g. `..` range syntax), though. That should be fixed in the future. Lastly, this commit adds support for parsing right-associative `<-` (left arrow) operator with precedence higher than assignment as the operator for placement-in feature.