4 releases (2 breaking)
|0.3.0||Sep 2, 2021|
|0.2.0||Jul 19, 2021|
|0.1.1||Mar 11, 2021|
|0.1.0||Aug 14, 2020|
#127 in Concurrency
22 downloads per month
Used in kocheck
Kontroli (Esperanto for verify) is an alternative implementation of the logical framework Dedukti, concentrating on the verification of proofs.
Kontroli's use case is to verify proofs generated by automated reasoning tools, such as proof assistants and automated theorem provers. It serves to verify the output of Dedukti by providing a "second opinion" and to make it easier for users to understand and learn from the implementation. It is also a testbed for parallelising type checking.
Kontroli requires at least Rust 1.40. On a recent Ubuntu system, this can be installed via:
sudo apt install rustc
For other systems, instructions are available at https://rustup.rs/.
To run Kontroli on output generated from Isabelle/Pure:
cargo run --release examples/pure.dk
To install Kontroli:
cargo install --path kocheck
Kontroli provides a command-line program,
kocheck, and a library.
The latter means that you can use Kontroli as part of your own applications.
Given that the Kontroli library does not rely on Rust's standard library,
you could use it also in environments such as web pages,
offering type checking as a service.
Kontroli tries to be the following:
- Small: write as little code as possible ...
- Correct: ... because the code you do not write, contains no bugs
- Efficient: be at least as fast as Dedukti in main use case
- Compatible: stick to Dedukti's syntax/semantics as much as possible
- Conservative: use established and well-tested techniques
There are a few differences with respect to Dedukti:
- Kontroli has a module system allowing for nested modules.
- Kontroli does not support higher-order rewrite rules, as they would make the whole program considerably more complex, thus contradicting the idea of a small type checker.
- Kontroli assures the type-safety of rewrite rules only if all free pattern variables have type annotations.
- Kontroli does not use decision trees for rewriting.
- Kontroli does not have any commands like
#ASSERT, which are particularly used in Dedukti tests. Instead, tests in the code base are preferred.
A few useful commands for developing Kontroli:
- Generating documentation:
cargo doc --open
- Running tests:
- Running benchmarks:
cargo bench -p kontroli -- --sample-size 10