Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hash Calculations for Domains #578

Merged
merged 2 commits into from
May 19, 2022
Merged

Conversation

ArquintL
Copy link
Member

The hash of a domain should not depend on the precise ordering of its domain functions and domain axioms. This is important when performing cache lookups as a cached verification result can still safely be used even if the some domain functions are in a slightly different order

@JonasAlaif
Copy link
Contributor

Looks good to me, should we add a CI test that checks that the hash of two reordered domains stays the same?

@ArquintL
Copy link
Member Author

How easy would this be? I already have a unit test in ViperServer that checks whether verifying two input programs that only differ in the order of domain functions and/or axioms results in the latter one being cached

@mschwerhoff
Copy link
Contributor

As easy as adding another unit test to Silver:

Since hashes are computed over the Silver AST, the Silver repo seems a more natural location for such tests than the ViperServer repo. But I'd keep the ViperServer test nonetheless, it probably has more of an end-to-end test flavour.

@ArquintL ArquintL force-pushed the caching-modulo-domain-orderings branch from 0513ec3 to 1886df0 Compare May 19, 2022 12:34
@ArquintL ArquintL force-pushed the caching-modulo-domain-orderings branch from 1886df0 to 86b4811 Compare May 19, 2022 12:35
@ArquintL ArquintL merged commit c23f27c into master May 19, 2022
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.

3 participants