[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
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
[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
Comments (0)
No comments yet. Start the discussion.