Skip to content

Commit 5be5a88

Browse files
committed
Explain, why we want to use save-analysis at all
1 parent 2536b83 commit 5be5a88

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

posts/inside-rust/2019-11-19-ide-future.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,7 @@ Horizontally, `rustc` compiles one crate at a time; rust-analyzer uses queries f
4646
# Way forward
4747
Our current hypothesis is that it is possible to integrate both approaches without doubling the engineering effort.
4848
Specifically, we will add an option to rust-analyzer to use save-analysis for find-usages and rename functionality.
49+
That way, we'll get precise results for most important queries, without slowing down completion.
4950
Unlike RLS, however, rust-analyzer will not link to rustc and instead will rely on cargo for running the compiler and producing save-analysis data.
5051
If this approach works, we will consider freezing RLS and focusing fully on rust-analyzer.
5152
Long term, the plan is to unify the save-analysis fallback path and the lazy analysis.

0 commit comments

Comments
 (0)