Skip to content

Add support for quantifiers #3993

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

Open
wants to merge 21 commits into
base: main
Choose a base branch
from

Conversation

qinheping
Copy link
Contributor

This PR add support for quantifiers. Especially, we inline function calls in quantified expressions so that the result statement-expression can be accepted by the CBMC backend.

RFC: RFC 0010-quantifiers.

Resolves #2546 and #836.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

feliperodri and others added 3 commits April 7, 2025 06:25
Signed-off-by: Felipe R. Monteiro <felisous@amazon.com>
Signed-off-by: Felipe R. Monteiro <felisous@amazon.com>
@qinheping qinheping requested a review from a team as a code owner April 7, 2025 06:34
@github-actions github-actions bot added the Z-BenchCI Tag a PR to run benchmark CI label Apr 7, 2025
@@ -0,0 +1 @@
VERIFICATION:- SUCCESSFUL
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That by itself would not really make for a useful use of expected - can we check for particular properties that are being reported as proved, please?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviving this comment--please write expected tests instead that show that the quantifier is being evaluated and its properties are successful, and then I'll review.

Copy link
Contributor

@carolynzech carolynzech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've only looked at the tests so far. I'm not sure that this makes sense to merge if the only kinds of harnesses that we can run are the ones in no_array.rs. IMO the main benefit of quantifiers is quantifying over some collection (array, vector, ...), so we should either block this PR until that's possible, or I would expect to see some expected tests to prove that it works.
Also, can we move the tests to expected and have some assertions about particular properties that are being checked?

fn quantifier_even_harness() {
let j: isize = kani::any();
kani::assume(j % 2 == 0 && j < 2000 && j > -2000);
kani::assert(kani::exists!(|i in (-1000, 1000)| i + i == j), "");
Copy link
Member

@tautschnig tautschnig Apr 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am surprised this one is a "fixme" test - what is holding us up on this one? (Also, this one does not include a link to an issue.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Z-BenchCI Tag a PR to run benchmark CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Quantifiers for function contracts
5 participants