Add user friendly Kani driver messages #1899
Description
Use case: Messages inside Kani driver should have a proper category and follow standard format.
E.g.:
- Validation that fails due to user invalid input should not appear to be a Kani crash.
- No harnesses have been found by Kani.
Test case:
$ cargo new --lib pkg
$ cd pkg
$ cargo kani -p wrong_name
thread 'main' panicked at 'Cannot find package 'wrong_name'', kani-driver/src/call_cargo.rs:151:22
note: run with `RUST_BACKTRACE=1` environment variable to display a backtraceInstead, I expected a more friendly error that doesn't look like Kani bug. E.g.:
$ cargo build -p wrong_name
error: package ID specification `wrong_name` did not match any packages