apalache icon indicating copy to clipboard operation
apalache copied to clipboard

Document the behavior and expectations of the various caches

Open Kukovec opened this issue 2 years ago • 7 comments

Currently, it's not very clear what the caches do and where they're written to/read from.

Kukovec avatar Jan 24 '23 15:01 Kukovec

Also relevant for #2137

thpani avatar Jan 25 '23 11:01 thpani

I am removing myself as an assignee in this issue, but happy to help if somebody takes a lead on this issue!

konnov avatar Feb 22 '23 08:02 konnov

@konnov Honestly, I doubt that anyone but you can do this within reasonable time.

thpani avatar Feb 22 '23 09:02 thpani

Yeah, but then it will not happen in a reasonable time frame. I just want to reflect reality here :)

konnov avatar Feb 22 '23 09:02 konnov

As per our discussion last week, @Kukovec or @thpani are to update this issue with more specifics on what we need documented, and then we will get Igor to help fill in these identified gaps.

shonfeder avatar Mar 27 '23 15:03 shonfeder

I think a good starting point, as mentioned by @Kukovec in the meeting, is to document

  • what each cache is used for
  • when each cache SHOULD be called
  • when each cache MUST be called / what items can be expected to be in-cache
  • when each cache is popped/cleared

thpani avatar Mar 28 '23 06:03 thpani

Adding to the above, caches will also be an issue in follow-ups to #2547, since arena/SMT splitting would require us to reevaluate the caches, as the cached values are cells (arena), but the cache constraints are in SMT.

Kukovec avatar Apr 28 '23 10:04 Kukovec