IssueRaiser

[Feature Request]: Persistent caches

One of the latest posts states: > One of the current peculiarities of rust-analyzer is that it doesn’t persist caches to disk. Opening project in rust-analyzer means waiting a dozen seconds while we process standard library and dependencies. And while that may be true when working with IDEs like VScode that are launched once and used for a long period of time, other workflows that involve editors like `vim` and closing/opening lots of windows that don't share `rust-analyzer`s state between each other is actually quite painful. Each time a new window is opened one has to sit and wait and for large repos that is quite a long period. P.S. Sorry if it's a duplicate

Posted by montekki on Jun 2, 2020, 7:19 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments

github (Other)

[Feature Request]: Persistent caches

montekkiJun 2, 2020, 7:19 PM

One of the latest posts states: > One of the current peculiarities of rust-analyzer is that it doesn’t persist caches to disk. Opening project in rust-analyzer means waiting a dozen seconds while we process standard library and dependencies. And while that may be true when working with IDEs like VScode that are launched once and used for a long period of time, other workflows that involve editors like `vim` and closing/opening lots of windows that don't share `rust-analyzer`s state between each other is actually quite painful. Each time a new window is opened one has to sit and wait and for large repos that is quite a long period. P.S. Sorry if it's a duplicate

Comments (0)

No comments yet. Start the discussion.

Comment on this issue