feat: formal verification of unsafe blocks #143
Draft
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.
This PR formally verifies of almost all unsafe blocks in code base. Related to #18. Covered unsafe blocks are correct in the sense described below.
Kani provides bit-precise bounded model checking of the given functions. This roughly means that it can prove that some assertion holds for all possible (bounded) cases. In particular, it can spot
See limitations for things that Kani can not deal with.
Proofs for
debug_expect_unchecked
andFrozenCopyMap
are omitted due to enormous resources needed for checking. The most resource heavy correctness proof ofMapping
takes around 40GB of RAM.Here's the last lines of the output of
/usr/bin/time -v cargo kani
: