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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Unify check_mismatches and check_types	Florian Diebold	2021-06-20	1	-6/+5
\|
*	internal: use minicore deref more	Aleksey Kladov	2021-06-18	1	-23/+19
\|
*	minor: use minicore	Aleksey Kladov	2021-06-18	1	-13/+9
\|
*	internal: add iterator to minicore	Aleksey Kladov	2021-06-16	1	-39/+8
\|
*	internal: add fn to minicore	Aleksey Kladov	2021-06-16	1	-34/+30
\|
*	internal: switch some tests to minicore	Aleksey Kladov	2021-06-15	1	-26/+22
\|
*	internal: switch some tests to minicore	Aleksey Kladov	2021-06-15	1	-26/+24
\|
*	Implement per-edition preludes	Jonas Schievink	2021-06-01	1	-4/+5
\|
*	Deal with goals arising from unification	Florian Diebold	2021-05-21	1	-1/+1
\|
*	Get rid of resolve_ty_as_possible	Florian Diebold	2021-05-21	1	-8/+8
\| \| \| \|	Instead use shallow resolving where necessary.
*	Update tests with expected changes	Florian Diebold	2021-05-21	1	-37/+34
\|
*	Merge #8799	bors[bot]	2021-05-12	1	-6/+6
\|\ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	8799: Add basic support for array lengths in types r=flodiebold a=lf- This recognizes `let a = [1u8, 2, 3]` as having type `[u8; 3]` instead of the previous `[u8; _]`. Byte strings and `[0u8; 2]` kinds of range array declarations are unsupported as before. I don't know why a bunch of our rustc tests had single quotes inside strings un-escaped by `UPDATE_EXPECT=1 cargo t`, but I don't think it's bad? Maybe something in a nightly? Co-authored-by: Jade <[email protected]>
\| *	Add basic support for array lengths in types	Jade	2021-05-11	1	-6/+6
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This recognizes `let a = [1u8, 2, 3]` as having type `[u8; 3]` instead of the previous `[u8; _]`. Byte strings and `[0u8; 2]` kinds of range array declarations are unsupported as before. I don't know why a bunch of our rustc tests had single quotes inside strings un-escaped by `UPDATE_EXPECT=1 cargo t`, but I don't think it's bad? Maybe something in a nightly?
* \|	Add a test for conditionally compiled tails	Daniel McNab	2021-05-03	1	-0/+49
\|/
*	Don't look in super traits for <T as Trait>::Assoc	Florian Diebold	2021-04-29	1	-0/+8
\| \| \| \| \| \| \|	This isn't actually how it works, you have to specify the exact trait that has the associated type. Fixes #8686.
*	Add test for #8686	Florian Diebold	2021-04-29	1	-0/+30
\|
*	Fix crash on syn involving lifetimes returned by Chalk	Florian Diebold	2021-04-09	1	-0/+38
\| \| \| \| \| \| \| \| \| \|	If we get lifetime variables back in autoderef, just immediately replace them by static lifetimes for now. Method resolution doesn't really deal correctly with new variables being introduced (this needs to be fixed more properly). This fixes `rust-analyzer analysis-stats --with-deps` crashing in the RA repo.
*	resolver: manually traverse nested block scopes	Jonas Schievink	2021-03-22	1	-0/+13
\|
*	Use upstream cov-mark	Laurențiu Nicola	2021-03-08	1	-4/+3
\|
*	Fix infer error of macro invocation in array expr	Edwin Cheng	2021-01-02	1	-0/+18
\|
*	Add regression test	Edwin Cheng	2020-12-15	1	-0/+24
\|
*	Add test for #6852	Florian Diebold	2020-12-13	1	-0/+37
\|
*	Upgrade Chalk	Florian Diebold	2020-12-07	1	-0/+43
\| \| \| \| \| \| \|	Also make overflow depth and max type size configurable through env variables. This can be helpful at least for debugging. Fixes #6628.
*	Switch to expect_test from crates.io	Aleksey Kladov	2020-08-21	1	-1/+1
\|
*	Rename ra_hir_ty -> hir_ty	Aleksey Kladov	2020-08-13	1	-0/+842