runtimeverification / runtimeverification/kontrol
Don't require build to run proofs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
The sensible behavior from a user perspective is that if there needs to be a kontrol build, it should just be run automatically. Ideally it should happen if any relevant source file has changed, but just running build if any files have changed since last build is also a sensible behavior.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the proof-running entry point and trace how it currently detects or reports a missing build. Then inspect the existing kontrol build command and determine how changed files are tracked. Done means proofs automatically trigger a build when needed, including the simpler case where any file changed since the last build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100