Proposed change: Deprecate the recently added kani::check function that generates non-fatal properties. I believe this was accidentally added as a new stable function as part of the uninitialized memory checks work.
Motivation: I don't think we have a clear use-case for this API today, and this will likely cause more confusion around which API to use, assertion vs cover vs check.
I'm OK keeping this internal to Kani for cases where we implement checks using demonic non-determinism to ensure some conditions are never violated.
Note: I have changed my mind since I created #695. I think cover is a much better fit for the cases I originally had in mind.
Proposed change: Deprecate the recently added
kani::checkfunction that generates non-fatal properties. I believe this was accidentally added as a new stable function as part of the uninitialized memory checks work.Motivation: I don't think we have a clear use-case for this API today, and this will likely cause more confusion around which API to use, assertion vs cover vs check.
I'm OK keeping this internal to Kani for cases where we implement checks using demonic non-determinism to ensure some conditions are never violated.
Note: I have changed my mind since I created #695. I think
coveris a much better fit for the cases I originally had in mind.