Skip to content

Conversation

julienduchesne
Copy link
Collaborator

Closes #133

There are two caches currently:

  • One for protocol documents. This one is instantiated by the server and maintained up-to-date as documents are opened, changed, and closed.
  • One for jsonnet objects. This one is a global var and is only added to. Modified objects are never removed/modified from the cache.

By merging the two caches, we can expand the first cache's behavior to also invalidate modified objects from the global cache when a document is changed.

Closes #133

There are two caches currently:
- One for protocol documents. This one is instantiated by the server and maintained up-to-date as documents are opened, changed, and closed.
- One for jsonnet objects. This one is a global var and is only added to. Modified objects are never removed/modified from the cache.

By merging the two caches, we can expand the first cache's behavior to also invalidate modified objects from the global cache when a document is changed.
julienduchesne and others added 2 commits August 25, 2024 21:04
Instead of carrying a `cache` and `vm` around on each function, create a `Processor` struct to contain those
@julienduchesne julienduchesne merged commit 6f0feae into main Aug 26, 2024
3 checks passed
@julienduchesne julienduchesne deleted the julienduchesne/global-cache branch August 26, 2024 01:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Re-read imported functions
1 participant