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

	Commit message (Collapse)	Author	Age	Files	Lines
*	fix panic on ellipsis in pattern	Josh Mcguigan	2020-04-17	1	-0/+49
\|
*	Handle `Self::Type` in trait definitions when referring to own associated type	Florian Diebold	2020-04-13	1	-2/+1
\| \| \| \|	It was implemented for other generic parameters for the trait, but not for `Self`.
*	Hide unit fn return types	Laurențiu Nicola	2020-04-05	1	-1/+1
\|
*	Add inference for literal and range patterns	Florian Diebold	2020-04-01	1	-1/+2
\|
*	Move test to hir_ty	Edwin Cheng	2020-03-21	1	-0/+31
\|
*	Fix printing of function types	Florian Diebold	2020-02-07	1	-1/+1
\|
*	Standard formatting for array types	Aleksey Kladov	2020-01-28	1	-4/+4
\|
*	Fix various names, e.g. Iterator not resolving in core prelude	Florian Diebold	2020-01-11	1	-0/+54
\| \| \| \| \| \| \| \| \| \| \| \| \|	Basically, `Iterator` is re-exported via several steps, which happened to not be resolved yet when we got to the prelude import, but since the name resolved to the reexport from `core::iter` (just to no actual items), we gave up trying to resolve it further. Maybe part of the problem is that we can have `PartialResolvedImport::Unresolved` or `PartialResolvedImport::Indeterminate` with `None` in all namespaces, and handle them differently. Fixes #2683.
*	Expand PAREN_EXPR as expression	Edwin Cheng	2020-01-10	1	-0/+17
\|
*	Fix #2705	Florian Diebold	2020-01-03	1	-0/+17
\| \| \| \| \| \| \| \|	The `-` turned into a `+` during a refactoring. The original issue was caused by `Read` resolving wrongly to a trait without type parameters instead of a struct with one parameter; this only fixes the crash, not the wrong resolution.
*	Don't add non-impl/trait containers to scope	Aleksey Kladov	2019-12-29	1	-1/+35
\|
*	Split up ty tests a bit	Florian Diebold	2019-12-03	1	-0/+333