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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add tests and only traverse in the crates directory	DJMcNab	2018-12-19	4	-87/+168
\|
*	Move is_block to lower in the call tree	DJMcNab	2018-12-19	2	-61/+61
\|
*	Fix parsing of inclusive ranges (#214)	DJMcNab	2018-12-19	2	-27/+65
\| \| \| \|	I'm not certain that this is correct, so extra eyes would be good
*	Fixed cast expression parsing in ra_syntax.	Roland Ruckerbauer	2018-12-17	2	-6/+48
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The cast expression expected any type via types::type_() function, but the language spec does only allow TypeNoBounds (types without direct extra bounds via `+`). Example: ```rust fn test() { 6i8 as i32 + 5; } ``` This fails, because the types::type_() function which should parse the type after the as keyword is greedy, and takes all plus sign after path types as extra. My proposed fix is to replace the not implemented `type_no_plus()` just calls (`type_()`) function, which is used at several places. The replacement is `type_with_bounds_cond(p: &mut Parser, allow_bounds: bool)`, which passes the condition to relevant sub-parsers. This function is then called by `type_()` and the new public `type_no_bounds()`.
*	Update use path test	DJMcNab	2018-12-05	2	-74/+2
\|
*	Improve/add the use_item documentation	DJMcNab	2018-12-05	10	-0/+485
\|
*	rename ROOT -> SOURCE_FILE	Aleksey Kladov	2018-11-07	113	-113/+113
\|
*	grammar: for predicates in where	Aleksey Kladov	2018-11-05	2	-0/+62
\| \| \| \|	closes #191
*	Support leading pipe in match arms	Daniel McNab	2018-10-03	2	-12/+56
\|
*	support 2018 paths	Aleksey Kladov	2018-09-29	2	-0/+16
\|
*	generate testsuite for impl_type	csmoe	2018-09-26	2	-0/+83
\|
*	rename all things	Aleksey Kladov	2018-09-16	219	-0/+5401