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

Global verification conditions #2525

Open
adpaco-aws opened this issue Jun 13, 2023 · 0 comments
Open

Global verification conditions #2525

adpaco-aws opened this issue Jun 13, 2023 · 0 comments
Labels
[C] Feature / Enhancement A new feature request or enhancement to an existing feature.

Comments

@adpaco-aws
Copy link
Contributor

Requested feature: Properties/Checks whose status depends on the status of other Kani properties/checks deserves a special section Kani's output. For example, the #[kani::should_panic] attribute could just be one of these, which we're calling "global conditions". This would allow us to keep a uniform UI to report their status and give feedback to users.
Use case: As mentioned, the #[kani::should_panic] attribute can be updated to be a global condition. Another one we have in mind is the option in #2299.
Link to relevant documentation (Rust reference, Nomicon, RFC): the #[kani::should_panic] attribute

Test case: N/A

@adpaco-aws adpaco-aws added the [C] Feature / Enhancement A new feature request or enhancement to an existing feature. label Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[C] Feature / Enhancement A new feature request or enhancement to an existing feature.
Projects
None yet
Development

No branches or pull requests

1 participant