Update README with Kani proofs #356
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MatiasVara
requested review from
alexandruag,
andreeaflorescu,
jiangliu,
slp,
stsquad,
epilys and
stefano-garzarella
as code owners
epilys
force-pushed
the
update_readme_with_kani
branch
from
443f5a9 to
6f4a290
Compare
MatiasVara
force-pushed
the
update_readme_with_kani
branch
2 times, most recently
from
85f029a to
4c9a725
Compare
epilys
reviewed
Jul 31, 2025
|
@MatiasVara can you also rebase? |
Update README with Kani proofs. Signed-off-by: Matias Ezequiel Vara Larsen <[email protected]>
MatiasVara
force-pushed
the
update_readme_with_kani
branch
from
4c9a725 to
45f4ef1
Compare
epilys
approved these changes
Jul 31, 2025
stefano-garzarella
approved these changes
Aug 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the PR
Update README with existing Kani proofs. This PR is regarding the addition of the first proof at #338. I am not sure if the README shall mention the existing PRs because that will force people to keep it update. At the same time, it may be useful for users to know which requirements from the specification are proved to be conform to.
Closes: #353
Requirements
Before submitting your PR, please make sure you addressed the following
requirements:
git commit -s), and the commit message has max 60 characters for thesummary and max 75 characters for each description line.
test.
Release" section of CHANGELOG.md (if no such section exists, please create one).
unsafecode is properly documented.