forked from JabRef/jabref
-
Notifications
You must be signed in to change notification settings - Fork 0
Caching #47
Copy link
Copy link
Open
Labels
component: LSPprio: esotericLow-prio, not a popular featureLow-prio, not a popular featureprio: post-gsoctype: featureNew feature or requestNew feature or requesttype: task
Metadata
Metadata
Assignees
Labels
component: LSPprio: esotericLow-prio, not a popular featureLow-prio, not a popular featureprio: post-gsoctype: featureNew feature or requestNew feature or requesttype: task
This may be a niche issue, but I think it's important to address:
Many programs use caches to improve performance by reducing the need to recalculate information. LSP servers can benefit from this approach as well.
However, if you introduce a caching mechanism, please ensure that caches are persisted to disk. I have extensive experience with Rust, and its LSP server never stores intermediate results or compilation data between sessions. Every time I reopen a project (after working one day, then returning the next), I have to wait about 5 minutes for all dependencies to be analyzed and compiled again.
This is worth keeping in mind. You can see how popular this feature request is in this issue: rust-lang/rust-analyzer#4712