package lambdapi
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=66d7d29f7a0d10493b8178c4c3aeb247971e24fab3eba1c54887e1b9a82fe005
sha512=69ecf2406e4c7225ab7f8ebe11624db5d2ab989c8f30f5b6e5d426fd8ef9102f142a2840af16fb9103bb712ebcf7d314635f8b413a05df66e7b7a38548867032
Description
This package provides:
- A lambdapi command for checking .lp or .dk files, translating .dk files to .lp files, or launching an LSP server for editing .lp files.
- A rich Emacs mode based on LSP (available on MELPA too).
- A very basic mode for Vim.
- OCaml libraries. A VSCode extension is also available on the VSCode Marketplace.
Find Lambdapi user manual on https://lambdapi.readthedocs.io/.
Lambdapi provides a rich type system with dependent types. In Lambdapi, one can define both type and function symbols by using rewriting rules (oriented equations). The declaration of symbols and rewriting rules is separated so that one can easily define inductive-recursive types for instance. Rewrite rules can be exported to the TRS and XTC formats for checking confluence and termination with external tools. A symbol can be declared associative and commutative. Lambdapi supports unicode symbols and infix operators.
Lambdapi does not come with a pre-defined logic. It is a powerful logical framework in which one can easily define its own logic and build and check proofs in this logic. There exist .lp files defining first or higher-order logic and complex type systems like in Coq or Agda.
Lambdapi provides a basic module and package system, interactive modes for proving both unification goals and typing goals, and tactics for solving them step by step. In particular, a rewrite tactic like in SSReflect, and a why3 tactic for calling external automated provers through the Why3 platform.
Published: 14 Dec 2021
README
Lambdapi, a proof assistant based on the λΠ-calculus modulo rewriting
>>>>>
User Manual <<<<<
Issues can be reported on the following issue tracker.
Questions can be asked on the following forum.
Examples of developments made with Lambdapi:
tests/OK
directory (used for testing and continuous integration)
Operating systems
Lambdapi requires a Unix-like system. It should work on Linux as well as on MacOS. It might be possible to make it work on Windows too with Cygwin or "bash on Windows".
Installation via Opam
Lambdapi is under active development. A new version of the lambdapi
Opam package will be released soon. For now, we advise to pin the development repository to get the latest development version:
opam pin add lambdapi https://github.com/Deducteam/lambdapi.git
opam install lambdapi # install emacs and vim support as well
The VSCode extension is available on the Marketplace.
The installation gives you:
a main executable
lambdapi
in yourPATH
OCaml libraries
a
lambdapi
mode forvim
a
lambdapi
mode foremacs
To browse the source code documentation, you can do:
opam install odig
odig doc lambdapi
Compilation from the sources
You can get the sources using git
as follows:
git clone https://github.com/Deducteam/lambdapi.git
Dependencies are described in lambdapi.opam
. The command why3 config detect
must be run to make Why3 know the available provers.
Using Opam, a suitable OCaml environment can be setup as follows:
opam install dune bindlib timed sedlex menhir pratter yojson cmdliner why3 alcotest alt-ergo odoc
why3 config detect
To compile Lambdapi, just run the command make
in the source directory. This produces the _build/install/default/bin/lambdapi
binary. Use the --help
option for more information. Other make targets are:
make # Build lambdapi
make doc # Build the user documentation (avalaible on readthedocs)
make odoc # Build the developer documentation
make install # Install lambdapi
make install_emacs # Install emacs mode
make install_vscode # Install vscode extension
make install_vim # Install vim support
Note: you can run lambdapi
without installing it with dune exec -- lambdapi
.
For running tests, one also needs alcotest and alt-ergo.
For building the source code documentation, one needs odoc. The starting file of the source code html documentation is _build/default/_doc/_html/lambdapi/index.html
.
For building the User Manual, see docs/README.md
.
The following commands can be used to clean up the repository:
make clean # Removes files generated by OCaml.
make distclean # Same as clean, but also removes library checking files.
make fullclean # Same as distclean, but also removes downloaded libraries.
Dependencies (12)
Used by
None
Conflicts
None