You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kani is now sure we've unwound the loop enough to verify our proof harness, and now we're seeing just the bound checking failures from the off-by-one error.
81
81
82
82
1. Exercise: Fix the off-by-one bounds error and get Kani to verify successfully.
83
-
2. Exercise: After fixing the error, `--unwind 11` works. Why?
83
+
2. Exercise: After fixing the error, `--default-unwind 11` works. Why?
Copy file name to clipboardExpand all lines: docs/src/tutorial-real-code.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ Running Kani on this simple starting point will help figure out:
77
77
2. Whether you're over-constrained. Check the coverage report using `--visualize`. Ideally you'd see 100% coverage, and if not, it's usually because now you've over-constrained the inputs.
78
78
3. Whether Kani will support all the Rust features involved.
79
79
4. Whether you've started with a tractable problem.
80
-
(If the problem is initially intractable, try `--unwind 1` and see if you can follow the techniques in the previous section to put a bound on the problem.)
80
+
(If the problem is initially intractable, try `--default-unwind 1` and see if you can follow the techniques in the previous section to put a bound on the problem.)
81
81
82
82
Once you've got something working, the next step is to prove more interesting properties than what Kani covers by default.
83
83
You accomplish this by adding new assertions (not just in your harness, but also to the code being run).
0 commit comments