Open jaisnan opened 1 year ago
If there's no way to run a single harness without ensuring that only that harness is run, maybe we could throw a warning to rename the harness to something unique (could modify the function ourselves before running the query).
That's a good point. Can you see how the rust vscode plugin handle that?
The changes to https://github.com/model-checking/kani/pull/2202 change how
kani x.rs --harness "y"
output looks like, and now it returns a fuzzy result, the extension needs to search for the exact harness.For example,
if there are two functions
the extension queries the output from kani for both the harnesses with the command
kani x.rs --harness function_1