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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Merge cli and ra_lsp_server	Aleksey Kladov	2020-02-17	1	-127/+0
\|
*	Use anyhow	Aleksey Kladov	2020-02-17	1	-1/+2
\|
*	Cleanup	Aleksey Kladov	2020-02-17	1	-42/+11
\|
*	Unify verbosity handling	Aleksey Kladov	2020-02-17	1	-5/+5
\|
*	Inline ra_batch	Aleksey Kladov	2020-02-17	1	-2/+2
\|
*	1-based columns	Aleksey Kladov	2020-02-16	1	-1/+1
\|
*	Support goto def in bences	Aleksey Kladov	2020-02-16	1	-6/+21
\|
*	Refactor position parsing	Aleksey Kladov	2020-02-16	1	-4/+25
\|
*	Enable profiling for bench	Aleksey Kladov	2020-02-16	1	-0/+2
\|
*	rename ra_ide_api -> ra_ide	Aleksey Kladov	2019-11-27	1	-1/+1
\|
*	:arrow_up: salsa	Aleksey Kladov	2019-11-26	1	-2/+2
\|
*	Prepare SourceDatabase API for lazy file loading	Aleksey Kladov	2019-10-14	1	-1/+1
\|
*	Added test for check doc strings in crates.	Alexander Andreev	2019-09-30	1	-0/+2
\| \| \| \|	#1856
*	make source_root API more abstract	Aleksey Kladov	2019-09-06	1	-2/+3
\|
*	implement durability	Aleksey Kladov	2019-08-15	1	-7/+31
\|
*	Make Analysis api cancellable	Kirill Bulatov	2019-07-25	1	-1/+1
\|
*	allow rustfmt to reorder imports	Aleksey Kladov	2019-07-04	1	-3/+3
\| \| \| \| \| \|	This wasn't a right decision in the first place, the feature flag was broken in the last rustfmt release, and syntax highlighting of imports is more important anyway
*	add analysis-bench to benchmark incremental analysis	Aleksey Kladov	2019-06-16	1	-0/+92
	Can be used like this: ``` $ cargo run --release -p ra_cli -- \ analysis-bench ../chalk/ \ --complete ../chalk/chalk-engine/src/logic.rs:94:0 loading: 225.970093ms from scratch: 8.492373325s no change: 445.265µs trivial change: 95.631242ms ``` Or like this: ``` $ cargo run --release -p ra_cli -- \ analysis-bench ../chalk/ \ --highlight ../chalk/chalk-engine/src/logic.rs loading: 209.873484ms from scratch: 9.504916942s no change: 7.731119ms trivial change: 124.984039ms ``` "from scratch" includes initial analysis of the relevant bits of the project "no change" just asks the same question for the second time. It measures overhead on assembling the answer outside of salsa. "trivial change" doesn't do an actual salsa change, it just advances the revision. This test how fast is salsa at validating things.