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

Age	Commit message (Collapse)	Author	Lines
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.