bors[bot] b1cb4ac13d Merge #5693 ... 5693: Fix no inlay hints / unresolved tokens until manual edit to refresh r=jonas-schievink a=Veetaha Fixes https://github.com/rust-analyzer/rust-analyzer/issues/5349 Now 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. Here are the examples before/after the change (the gifs are quite lengthy because they show testing rather large cargo workspace). <details> <summary>Before</summary> Here you can see that the client receives empty array of inlay hints and does nothing more. Same applies to semantic tokens. The client receives unresolved tokens and does nothing more. The user needs to do a manual edit to refresh the editor.  </details> <details> <summary>After</summary> Here the server returns ContentModified, so the client periodically retries the requests and eventually receives the wellformed response.  </details> Co-authored-by: Veetaha <veetaha2@gmail.com>		2020-08-09 22:39:10 +00:00
..
src	Merge #5693	2020-08-09 22:39:10 +00:00
test_data	Mark machine applicable fixes as preferred	2020-07-16 10:51:25 -04:00
tests/heavy_tests	Run package-specific cargo check and test for all targets	2020-07-29 15:35:27 +03:00
build.rs
Cargo.toml	Bump perf-event and rustc_lexer	2020-07-30 20:36:03 +03:00