Create --list-harnessesAPI
#1612
Comments
This was referenced Sep 7, 2022
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 3, 2024
RFC for the `kani list` subcommand. I saw the comment [in the template](https://github.com/model-checking/kani/blob/main/rfc/src/template.md#software-design) to leave the Software Design section empty, but I was looking at the raw MD file and made the mistake of thinking it referred to all sections below the comment. In other words, I thought when it said "We recommend you to leave this empty for the first version of your RFC" it meant that everything below the comment should be empty (so Rationale, Open Questions, and Future Work) and not Software Design. I realized my mistake when I was making this PR, but I figured I may as well leave it since I already wrote it. I [opened a PR](#3462) to update the comment. Resolves [#2573](#2573), [#1612](##1612). By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The VSCode extension needs a
--list-harnessesflag from Kani which gives a list of the metadata on all present harnesses in a crate. While this API is intended to be consumed by the VSCode extension, there could be other uses for it too.The text was updated successfully, but these errors were encountered: