History

Veetaha e43811c164 Fix no inlay hints / unresolved tokens until manual edit 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.		2020-08-08 21:53:38 +03:00
..
src	Fix no inlay hints / unresolved tokens until manual edit	2020-08-08 21:53:38 +03:00
tests	Disable ES module interop	2020-07-06 14:29:19 +03:00
.eslintrc.js
.gitignore
.vscodeignore	vscode client side tests	2020-05-20 22:31:39 +03:00
icon.png
package-lock.json	Bump lodash from 4.17.15 to 4.17.19 in /editors/code	2020-07-16 10:05:46 +00:00
package.json	Fix typo in settings description	2020-08-08 11:57:54 +02:00
ra_syntax_tree.tmGrammar.json	Fix .rast tmGrammar to account for numbers in identifiers	2020-04-22 02:00:58 +03:00
README.md
rollup.config.js	Bump @rollup/plugin-commonjs	2020-06-27 22:37:03 +03:00
rust.tmGrammar.json	Fix a typo	2020-06-30 17:42:54 +02:00
tsconfig.json	Disable ES module interop	2020-07-06 14:29:19 +03:00

rust-analyzer

Provides support for rust-analyzer: novel LSP server for the Rust programming language.