rust-analyzer - [FORK] modified to work on wasm targets

	Commit message (Collapse)	Author	Age	Files	Lines
*	[#1083] Try block syntax	Andrey Tkachenko	2019-06-06	1	-0/+7
\|
*	fixed macro for brackets	Sergey Parilin	2019-05-15	1	-2/+2
\|
*	Implemented T! macro for syntax kinds	Sergey Parilin	2019-05-13	1	-0/+95
\|
*	Add MacroItems and MacroStmts in grammer.ron	Edwin Cheng	2019-04-18	1	-0/+4
\|
*	Merge #1138	bors[bot]	2019-04-14	1	-0/+4
\|\ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	1138: Add L_DOLLAR and R_DOLLAR r=matklad a=edwin0cheng As discussion in issue https://github.com/rust-analyzer/rust-analyzer/issues/1132 and PR #1125 , this PR add 2 `Syntax::Kind` : `L_DOLLAR` and `R_DOLLAR` for representing `Delimiter::None` in mbe and proc_marco. By design, It should not affect the final syntax tree, and will be discard in `TreeSink`. My original idea is handling these 2 tokens case by case, but i found that they will appear in every place in the parser (imagine `tt` matcher). So this PR only handle it in `Parser::do_bump` and `Parser::start`, although It will not fix the `expr` matcher executing order problem in original idea. Co-authored-by: Edwin Cheng <[email protected]>
\| *	Add L_DOLLAR and R_DOLLAR	Edwin Cheng	2019-04-11	1	-0/+4
\| \|
* \|	migrate to untyped rowan	Aleksey Kladov	2019-04-09	1	-0/+18
\|/
*	Add new TYPE_BOUND_LIST and TYPE_BOUND syntax kinds	Ville Penttinen	2019-03-30	1	-0/+4
\| \| \| \| \| \|	These are now used when parsing type bounds. In addition parsing paths inside a bound now does not recursively parse paths, rather they are treated as separate bounds, separated by +.
*	Add async keyword	Caio	2019-03-09	1	-0/+4
\|
*	rename type to type_alias in the AST as well	Aleksey Kladov	2019-02-25	1	-2/+2
\|
*	move parser to a separate crate	Aleksey Kladov	2019-02-21	1	-0/+642