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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Latest proposed LSP 3.16.0	kjeremy	2020-10-26	1	-3/+2
\| \| \| \|	Needs: https://github.com/gluon-lang/lsp-types/pull/183
*	Move to vscode-languageclient 7.0.0-next.9	kjeremy	2020-09-02	1	-1/+1
\| \| \| \|	Stabilizes call hierarchy and semantic tokens features.
*	Dont ask me why...	Veetaha	2020-08-21	1	-1/+0
\|
*	Fix no inlay hints / unresolved tokens until manual edit	Veetaha	2020-08-08	1	-3/+3
\| \| \| \| \| \| \| \| \| \|	No we return ContentModified during the workspace loading. This signifies the language client to retry the operation (i.e. the client will continue polling the server while it returns ContentModified). I believe that there might be cases of overly big projects where the backoff logic we have setup in `sendRequestWithRetry` (which we use for inlay hints) might bail too early (currently the largest retry standby time is 10 seconds). However, I've tried on one of my project with 500+ dependencies and it is still enough.
*	Fix: allow for binaries from $PATH to pass validity check	Veetaha	2020-07-06	1	-6/+2
\|
*	Revert "Dispose logger on extension deactivation"	Veetaha	2020-07-05	1	-4/+0
\| \| \| \| \|	This reverts commit 13872543e074adc153b440660beda441fd562f53. That commit was wrong because we use-after-free the logger
*	Dispose logger on extension deactivation	Veetaha	2020-07-05	1	-0/+4
\|
*	Improve client logging (use output channel and more log levels)	Veetaha	2020-07-05	1	-10/+41
\|
*	Never disable error logging on the frontend	Veetaha	2020-06-22	1	-1/+0
\|
*	Change Runnable.bin -> Runnable.kind	veetaha	2020-05-31	1	-0/+18
\| \| \| \| \| \|	As per matklad, we now pass the responsibility for finding the binary to the frontend. Also, added caching for finding the binary path to reduce the amount of filesystem interactions.
*	Add `inRustProject` when-clause for commands.	vsrs	2020-05-27	1	-0/+5
\|
*	Partially fix displaying inlay hints in Github PR diff views	veetaha	2020-05-26	1	-4/+5
\|
*	Fix cargo not found on macos bug at vscode extension side	veetaha	2020-05-06	1	-0/+11
\|
*	vscode: add syntax tree inspection hovers and highlights	veetaha	2020-03-31	1	-2/+2
\|
*	Rewrite auto-update	Aleksey Kladov	2020-03-19	1	-54/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	Everything now happens in main.ts, in the bootstrap family of functions. The current flow is: * check everything only on extension installation. * if the user is on nightly channel, try to download the nightly extension and reload. * when we install nightly extension, we persist its release id, so that we can check if the current release is different. * if server binary was not downloaded by the current version of the extension, redownload it (we persist the version of ext that downloaded the server).
*	vscode-prerefactor: add some utility functions	Veetaha	2020-03-14	1	-6/+63
\|
*	vscode: prerefactor util.ts and ctx.ts	Veetaha	2020-03-07	1	-3/+9
\|
*	Centralize the check for languageId on document	Julien Roncaglia	2020-03-02	1	-0/+8
\| \| \| \|	Also move visibleRustEditors to Ctx
*	vscode: simplify assert.eq() to assert() as per matklad	Veetaha	2020-02-28	1	-11/+1
\|
*	vscode: add dat semicolon	Veetaha	2020-02-28	1	-1/+1
\|
*	vscode: add equality assertion	Veetaha	2020-02-28	1	-0/+10
\|
*	vscode: rename nodeAssert -> nativeAssert	Veetaha	2020-02-28	1	-2/+2
\|
*	vscode: add error loging on failed assertion	Veetaha	2020-02-28	1	-1/+6
\|
*	vscode: migrate to more type-safe assert impl	Veetaha	2020-02-28	1	-4/+8
\|
*	vscode: migrate inlay_hints to rust-analyzer-api.ts	Veetaha	2020-02-24	1	-8/+8
\|
*	vscode: gracefully handle cancellation errors	Veetaha	2020-02-23	1	-0/+40
\|
*	Extract client-side logging	Aleksey Kladov	2020-02-22	1	-0/+18