Deprecate standalone kani, add support for cargo-kani for every call #46
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.
Description of changes:
Switch to cargo-kani for all commands, and deprecate usage of standalone kani.
Call-outs:
Need to raise an issue or call out in documentation that we don't support standalone kani as a proof runner i.e we require that the extension be run on a crate with a declared cargo.toml. This is similar to how rust-analyzer handles it too, rust-lang/rust-analyzer#8818.
Testing:
How is this change tested? Manual testing
Is this a refactor change? Yes
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.