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

	Commit message (Collapse)	Author	Age	Files	Lines
...
* \| \| \| \|	Move ReqQueue to lsp-server	Aleksey Kladov	2020-06-20	6	-190/+107
\| \| \| \| \|
* \| \| \| \|	Merge #4961	bors[bot]	2020-06-20	4	-170/+188
\|\ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4961: Centralize handing of in-flight requests r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
\| * \| \| \| \|	Centralize handing of in-flight requests	Aleksey Kladov	2020-06-20	4	-170/+188
\| \| \| \| \| \|
* \| \| \| \| \|	Merge #4958	bors[bot]	2020-06-20	4	-24/+312
\|\ \ \ \ \ \ \| \|/ / / / / \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4958: Infer FnSig via Fn traits r=flodiebold a=adamrk Addresses https://github.com/rust-analyzer/rust-analyzer/issues/4481. When inferring types check if the callee implements one of the builtin `Fn` traits. Also autoderef the callee before trying to figure out it's `FnSig`. Co-authored-by: adamrk <[email protected]>
\| * \| \| \| \|	Push obligation instead of matching on solution	adamrk	2020-06-20	2	-45/+40
\| \| \| \| \| \|
\| * \| \| \| \|	Get Output assoc type by name	adamrk	2020-06-20	1	-13/+3
\| \| \| \| \| \|
\| * \| \| \| \|	Add test for dyn Fn Output	adamrk	2020-06-20	1	-0/+68
\| \| \| \| \| \|
\| * \| \| \| \|	move tests to ra_hir_ty	adamrk	2020-06-20	2	-104/+155
\| \| \| \| \| \|
\| * \| \| \| \|	Fixes to callable_sig_from_fn_trait	adamrk	2020-06-20	2	-67/+72
\| \| \| \| \| \|
\| * \| \| \| \|	Make get_fn_trait a method of FnTrait	adamrk	2020-06-20	3	-21/+21
\| \| \| \| \| \|
\| * \| \| \| \|	Switch back callable_sig for known fn types	adamrk	2020-06-20	2	-4/+4
\| \| \| \| \| \|
\| * \| \| \| \|	Infer FnSig from Fn traits	adamrk	2020-06-19	5	-18/+197
\| \| \| \| \| \|
* \| \| \| \| \|	Merge #4952	bors[bot]	2020-06-19	2	-0/+94
\|\ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4952: Shift bound variables correctly when using assoc type shorthand r=matklad a=flodiebold Fixes #4885. Fixes #4800. Co-authored-by: Florian Diebold <[email protected]>
\| * \| \| \| \| \|	Shift bound variables correctly when using assoc type shorthand	Florian Diebold	2020-06-19	2	-0/+94
\| \| \|_\|/ / / \| \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Fixes #4885. Fixes #4800.
* \| \| \| \| \|	Merge #4951	bors[bot]	2020-06-19	2	-6/+31
\|\ \ \ \ \ \ \| \|/ / / / / \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4951: Don't panic on crates depending on themselves r=matklad a=flodiebold Fixes #3883. Co-authored-by: Florian Diebold <[email protected]>
\| * \| \| \| \|	Don't panic on crates depending on themselves	Florian Diebold	2020-06-19	2	-6/+31
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Fixes #3883.
* \| \| \| \| \|	Use correct substs for super trait assoc types	Florian Diebold	2020-06-19	3	-17/+47
\| \|/ / / / \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	When referring to an associated type of a super trait, we used the substs of the subtrait. That led to the #4931 crash if the subtrait had less parameters, but it could also lead to other incorrectness if just the order was different. Fixes #4931.
* \| \| \| \|	Fix substs in resolve_value_path for ImplSelf	Vincent Rouillé	2020-06-19	2	-1/+33
\|/ / / / \| \| \| \| \| \| \| \| \| \| \| \|	Fixes #4953.
* \| \| \|	Merge #4851	bors[bot]	2020-06-19	5	-5/+134
\|\ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4851: Add quickfix to add a struct field r=TimoFreiberg a=TimoFreiberg Related to #4563 I created a quickfix for record literals first because the NoSuchField diagnostic was already there. To offer that quickfix for FieldExprs with unknown fields I'd need to add a new diagnostic (or create a `NoSuchField` diagnostic for those cases) I think it'd make sense to make this a snippet completion (to select the generated type), but this would require changing the `Analysis` API and I'd like some feedback before I touch that. Co-authored-by: Timo Freiberg <[email protected]>
\| * \| \| \|	Add quickfix to add a struct field	Timo Freiberg	2020-06-12	5	-5/+134
\| \| \| \| \|
* \| \| \| \|	Merge #4937	bors[bot]	2020-06-19	1	-1/+4
\|\ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4937: Allow overriding rust-analyzer display version r=matklad a=oxalica The build script invokes `git` for version information which is displayed when rust-analyzer is called with `--version`. But in build environment without `git` or when the source code is not a git repo, there's no way to manually specify the version information. This patch respects environment variable ~`REV`~ `RUST_ANALYZER_REV` in compile time for overriding. Related: https://github.com/NixOS/nixpkgs/pull/90976 Co-authored-by: oxalica <[email protected]>
\| * \| \| \| \|	Fix fmt	oxalica	2020-06-18	1	-1/+2
\| \| \| \| \| \|
\| * \| \| \| \|	Allow overriding rust-analyzer display revision	oxalica	2020-06-18	1	-1/+3
\| \| \| \| \| \|
* \| \| \| \| \|	Merge #4839	bors[bot]	2020-06-19	6	-36/+1335
\|\ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4839: `Go to Type Definition` hover action. r=matklad a=vsrs ![hover_actions_goto](https://user-images.githubusercontent.com/62505555/83335671-0122e380-a2b7-11ea-9922-fbdcfb11a7f3.gif) This implementation supports things like `dyn Trait<SomeType>`, `-> impl Trait`, etc. Co-authored-by: vsrs <[email protected]>
\| * \| \| \| \| \|	Apply suggestions from code review	vsrs	2020-06-18	3	-65/+328
\| \| \| \| \| \| \|
\| * \| \| \| \| \|	Add Type::walk method	vsrs	2020-06-18	3	-75/+132
\| \| \| \| \| \| \|
\| * \| \| \| \| \|	Remove AdtOrTrait	vsrs	2020-06-18	4	-50/+39
\| \| \| \| \| \| \|
\| * \| \| \| \| \|	Add associated type test.	vsrs	2020-06-18	1	-0/+57
\| \| \| \| \| \| \|
\| * \| \| \| \| \|	Fix type "items" order.	vsrs	2020-06-18	2	-24/+36
\| \| \| \| \| \| \|
\| * \| \| \| \| \|	Add `Go to Type Definition` hover action.	vsrs	2020-06-18	8	-35/+956
\| \| \| \| \| \| \|
\| * \| \| \| \| \|	Fix empty hover action group for a runnable.	vsrs	2020-06-18	1	-1/+1
\| \| \| \| \| \| \|
* \| \| \| \| \| \|	Speedup VFS::partition	Aleksey Kladov	2020-06-19	4	-11/+30
\| \|_\|_\|/ / / \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The task of `partition` function is to bin the flat list of paths into disjoint filesets. Ideally, it should be incremental -- each new file should be added to a specific fileset. However, preliminary measurnments show that it is actually fast enough if we just optimize this to use a binary search instead of a linear scan.
* \| \| \| \| \|	Merge #4930	bors[bot]	2020-06-18	1	-28/+49
\|\ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4930: Avoid all unchecked indexing in match checking r=flodiebold a=jonas-schievink Fixes https://github.com/rust-analyzer/rust-analyzer/issues/4416, but replaces it with a false positive. r? @flodiebold Co-authored-by: Jonas Schievink <[email protected]>
\| * \| \| \| \| \|	Avoid all unchecked indexing in match checking	Jonas Schievink	2020-06-17	1	-28/+49
\| \| \|_\|_\|/ / \| \|/\| \| \| \|
* \| \| \| \| \|	Merge #4941	bors[bot]	2020-06-18	2	-8/+4
\|\ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4941: Simplify r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
\| * \| \| \| \| \|	Simplify	Aleksey Kladov	2020-06-18	2	-8/+4
\| \| \|_\|/ / / \| \|/\| \| \| \|
* \| \| \| \| \|	Merge #4903	bors[bot]	2020-06-18	5	-41/+56
\|\ \ \ \ \ \ \| \|/ / / / / \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4903: Add highlighting support for doc comments r=matklad a=Nashenas88 The language server protocol includes a semantic modifier for documentation. This change exports that modifier for doc comments so users can choose to highlight them differently compared to regular comments. Example: <img width="375" alt="Screen Shot 2020-06-16 at 10 34 14 AM" src="https://user-images.githubusercontent.com/1673130/84788271-f6599580-afbc-11ea-96e5-7a0215da620b.png"> CC @woody77 Co-authored-by: Paul Daniel Faria <[email protected]>
\| * \| \| \| \|	Remove logic to mark all doctest code as	Paul Daniel Faria	2020-06-18	2	-14/+13
\| \| \| \| \| \|
\| * \| \| \| \|	Ensure all existing doctest code highlights have documentation modifier	Paul Daniel Faria	2020-06-17	3	-21/+22
\| \| \| \| \| \|
\| * \| \| \| \|	Add highlighting support for doc comments	Paul Daniel Faria	2020-06-17	5	-41/+56
\| \| \| \| \| \|
* \| \| \| \| \|	Merge #4935	bors[bot]	2020-06-18	2	-10/+4
\|\ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4935: Simplify r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
\| * \| \| \| \| \|	Simplify	Aleksey Kladov	2020-06-18	2	-10/+4
\| \| \|_\|/ / / \| \|/\| \| \| \|
* \| \| \| \| \|	Merge #4821	bors[bot]	2020-06-18	2	-9/+32
\|\ \ \ \ \ \ \| \|/ / / / / \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4821: display Doctest code lens before comment r=matklad a=bnjjj close #4785 Co-authored-by: Benjamin Coenen <[email protected]>
\| * \| \| \| \|	display Doctest code lens before comment #4785	Benjamin Coenen	2020-06-18	2	-9/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Signed-off-by: Benjamin Coenen <[email protected]>
\| * \| \| \| \|	display Doctest code lens before comment #4785	Benjamin Coenen	2020-06-14	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Signed-off-by: Benjamin Coenen <[email protected]>
\| * \| \| \| \|	display Doctest code lens before comment #4785	Benjamin Coenen	2020-06-09	2	-3/+32
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Signed-off-by: Benjamin Coenen <[email protected]>
* \| \| \| \| \|	Merge #4872	bors[bot]	2020-06-18	1	-46/+43
\|\ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4872: Reduce the usage of bare subscript operator r=matklad a=Veetaha Co-authored-by: Veetaha <[email protected]>
\| * \| \| \| \| \|	Reduce the usage of bare subscript operator	Veetaha	2020-06-14	1	-46/+43
\| \| \| \| \| \| \|
* \| \| \| \| \| \|	Merge #4934	bors[bot]	2020-06-18	6	-212/+69
\|\ \ \ \ \ \ \ \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	4934: Remove special casing for library symbols r=matklad a=matklad We might as well handle them internally, via queries. I am not sure, but it looks like the current LibraryData setup might even predate salsa? It's not really needed and creates a bunch of complexity. bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
\| * \| \| \| \| \| \|	Remove special casing for library symbols	Aleksey Kladov	2020-06-18	6	-212/+69
\| \| \|_\|_\|/ / / \| \|/\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	We might as well handle them internally, via queries. I am not sure, but it looks like the current LibraryData setup might even predate salsa? It's not really needed and creates a bunch of complexity.