-
Notifications
You must be signed in to change notification settings - Fork 92
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
Add implementation for the #[kani::should_panic]
attribute
#2315
Conversation
Changed the comments around |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @adpaco-aws! Looking forward to the documentation of this feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, forgot to submit one minor comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Trying to submit it again.
Description of changes:
This PR adds the implementation for the
#[kani::should_panic]
attribute.Using the attribute will return the following results:
VERIFICATION:- FAILED (encountered no panics, but at least one was expected)
if there were no failures.VERIFICATION:- FAILED (encountered failures other than panics, which were unexpected)
if there were failures but not all them hadprop.property_class() == "assertion"
.VERIFICATION:- SUCCESSFUL (encountered one or more panics as expected)
otherwise.Resolved issues:
Resolves #600
Related RFC:
#2272
Call-outs:
Testing:
How is this change tested? Existing tests + 6 new
ui
testsIs this a refactor change? No.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.