diff options
| author | bors <bors@rust-lang.org> | 2024-08-19 17:30:25 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-08-19 17:30:25 +0000 |
| commit | df6ce9607ca80cd2068393b0cb2178ae1c39c677 (patch) | |
| tree | e8e62d472f470bfee8c5216170075d79be04e4ef /tests/codegen/patchable-function-entry/patchable-function-entry-no-flag.rs | |
| parent | f9c0c8a7794b9a9679a82e95a8af67ba62948582 (diff) | |
| parent | f25cb8073c2a10648fff0a267e3c41817a81b1a0 (diff) | |
| download | rust-df6ce9607ca80cd2068393b0cb2178ae1c39c677.tar.gz rust-df6ce9607ca80cd2068393b0cb2178ae1c39c677.zip | |
Auto merge of #17886 - Wilfred:prime_caches_quiescent, r=Veykril
internal: ServerStatusParams should consider 'prime caches' in quiescent status Priming caches is a performance win, but it takes a lock on the salsa database and prevents rust-analyzer from responding to e.g. go-to-def requests. This causes confusion for users, who see the spinner next to rust-analyzer in the VS Code footer stop, so they start attempting to navigate their code. Instead, set the `quiescent` status in LSP to false during cache priming, so the VS Code spinner persists until we can respond to any LSP request.
Diffstat (limited to 'tests/codegen/patchable-function-entry/patchable-function-entry-no-flag.rs')
0 files changed, 0 insertions, 0 deletions