diff options
author | bors[bot] <bors[bot]@users.noreply.github.com> | 2019-06-16 09:08:10 +0100 |
---|---|---|
committer | bors[bot] <bors[bot]@users.noreply.github.com> | 2019-06-16 09:08:10 +0100 |
commit | e6fbff3246cdd3278ff1c376d5abfc1d579f86c2 (patch) | |
tree | 736052286d9c0d8d06798165590bdf145a12d783 /crates/ra_lsp_server/Cargo.toml | |
parent | ce9ea0939a1ae94a83d56ddafc7aeb757dcda776 (diff) | |
parent | b0be4207d04b65580e7af10cb256ddd5d9ca006d (diff) |
Merge #1406
1406: reuse AnalysisHost in batch analysis r=matklad a=matklad
We do some custom setup in `AnalysisHost`, like setting up LRU size. I figure it's a good idea to not duplicate this work in batch analysis, *if* we want to keep batch and non-batch close.
Long-term, I see a value in keeping batch a separate, lighter weight thing. However, because now we use batch to measure performance, keeping them closer makes more sense.
I'd also like to add ability to get completions by using batch analysis, and that will require ra_ide_api as well.
@flodiebold were there some reason why we haven't started with this approach from the start?
Co-authored-by: Aleksey Kladov <[email protected]>
Diffstat (limited to 'crates/ra_lsp_server/Cargo.toml')
0 files changed, 0 insertions, 0 deletions