commit ed2647490fb82f45cadf293cfce46a8cad6933cf · anil.recoil.org/opam-repository

+90
packages/elpi/elpi.2.0.2/opam
···

       1
       1
       +
       opam-version: "2.0"

     

       2
       2
       +
       maintainer: "Enrico Tassi <enrico.tassi@inria.fr>"

     

       3
       3
       +
       authors: [ "Claudio Sacerdoti Coen" "Enrico Tassi" ]

     

       4
       4
       +
       license: "LGPL-2.1-or-later"

     

       5
       5
       +
       homepage: "https://github.com/LPCIC/elpi"

     

       6
       6
       +
       doc: "https://LPCIC.github.io/elpi/"

     

       7
       7
       +
       dev-repo: "git+https://github.com/LPCIC/elpi.git"

     

       8
       8
       +
       bug-reports: "https://github.com/LPCIC/elpi/issues"

     

       9
       9
       +
       

     

       10
       10
       +
       build: [

     

       11
       11
       +
         ["dune" "subst"] {dev}

     

       12
       12
       +
         ["dune" "build" "-p" name "-j" jobs]

     

       13
       13
       +
         [make "tests" "DUNE_OPTS=-p %{name}%" "SKIP=performance_HO" "SKIP+=performance_FO" "SKIP+=elpi_api_performance"] {with-test & os != "macos" & os-distribution != "alpine" & os-distribution != "freebsd"}

     

       14
       14
       +
       ]

     

       15
       15
       +
       

     

       16
       16
       +
       depends: [

     

       17
       17
       +
         "ocaml" {>= "4.13.0" }

     

       18
       18
       +
         "stdlib-shims"

     

       19
       19
       +
         "ppxlib" {>= "0.12.0" }

     

       20
       20
       +
         "menhir" {>= "20211230" }

     

       21
       21
       +
         "re" {>= "1.7.2"}

     

       22
       22
       +
         "ppx_deriving" {>= "4.3"}

     

       23
       23
       +
         "ANSITerminal" {with-test}

     

       24
       24
       +
         "cmdliner" {with-test}

     

       25
       25
       +
         "fileutils" {with-test}

     

       26
       26
       +
         "dune" {>= "2.8.0"}

     

       27
       27
       +
         "conf-time" {with-test}

     

       28
       28
       +
         "atdgen" {>= "2.10.0"}

     

       29
       29
       +
         "atdts" {>= "2.10.0"}

     

       30
       30
       +
         "odoc" {with-doc}

     

       31
       31
       +
       ]

     

       32
       32
       +
       synopsis: "ELPI - Embeddable λProlog Interpreter"

     

       33
       33
       +
       description: """

     

       34
       34
       +
       ELPI implements a variant of λProlog enriched with Constraint Handling Rules,

     

       35
       35
       +
       a programming language well suited to manipulate syntax trees with binders.

     

       36
       36
       +
       

     

       37
       37
       +
       ELPI is designed to be embedded into larger applications written in OCaml as

     

       38
       38
       +
       an extension language. It comes with an API to drive the interpreter and 

     

       39
       39
       +
       with an FFI for defining built-in predicates and data types, as well as

     

       40
       40
       +
       quotations and similar goodies that are handy to adapt the language to the host

     

       41
       41
       +
       application.

     

       42
       42
       +
       

     

       43
       43
       +
       This package provides both a command line interpreter (elpi) and a library to

     

       44
       44
       +
       be linked in other applications (eg by passing -package elpi to ocamlfind).

     

       45
       45
       +
       

     

       46
       46
       +
       The ELPI programming language has the following features:

     

       47
       47
       +
       

     

       48
       48
       +
       - Native support for variable binding and substitution, via an Higher Order

     

       49
       49
       +
         Abstract Syntax (HOAS) embedding of the object language. The programmer

     

       50
       50
       +
         does not need to care about technical devices to handle bound variables,

     

       51
       51
       +
         like De Bruijn indices.

     

       52
       52
       +
       

     

       53
       53
       +
       - Native support for hypothetical context. When moving under a binder one can

     

       54
       54
       +
         attach to the bound variable extra information that is collected when the

     

       55
       55
       +
         variable gets out of scope. For example when writing a type-checker the

     

       56
       56
       +
         programmer needs not to care about managing the typing context.

     

       57
       57
       +
       

     

       58
       58
       +
       - Native support for higher order unification variables, again via HOAS.

     

       59
       59
       +
         Unification variables of the meta-language (λProlog) can be reused to

     

       60
       60
       +
         represent the unification variables of the object language. The programmer

     

       61
       61
       +
         does not need to care about the unification-variable assignment map and

     

       62
       62
       +
         cannot assign to a unification variable a term containing variables out of

     

       63
       63
       +
         scope, or build a circular assignment.

     

       64
       64
       +
       

     

       65
       65
       +
       - Native support for syntactic constraints and their meta-level handling rules.

     

       66
       66
       +
         The generative semantics of Prolog can be disabled by turning a goal into a

     

       67
       67
       +
         syntactic constraint (suspended goal). A syntactic constraint is resumed as

     

       68
       68
       +
         soon as relevant variables gets assigned. Syntactic constraints can be

     

       69
       69
       +
         manipulated by constraint handling rules (CHR).

     

       70
       70
       +
       

     

       71
       71
       +
       - Native support for backtracking. To ease implementation of search.

     

       72
       72
       +
       

     

       73
       73
       +
       - The constraint store is extensible.  The host application can declare

     

       74
       74
       +
         non-syntactic constraints and use custom constraint solvers to check their

     

       75
       75
       +
         consistency.

     

       76
       76
       +
       

     

       77
       77
       +
       - Clauses are graftable. The user is free to extend an existing program by

     

       78
       78
       +
         inserting/removing clauses, both at runtime (using implication) and at

     

       79
       79
       +
         "compilation" time by accumulating files.

     

       80
       80
       +
       

     

       81
       81
       +
       ELPI is free software released under the terms of LGPL 2.1 or above."""

     

       82
       82
       +
       url {

     

       83
       83
       +
         src:

     

       84
       84
       +
           "https://github.com/LPCIC/elpi/releases/download/v2.0.2/elpi-2.0.2.tbz"

     

       85
       85
       +
         checksum: [

     

       86
       86
       +
           "sha256=0b5b1f2eeed6b310bfa02039cede5fa51d0008f8d9ff47b51a63bc3e55200b53"

     

       87
       87
       +
           "sha512=4e757b70215082293053c33e4047dd9ba52b90d3ec80662d4fc1df656071edfb433b62ea2168331e9a52eddd6b0232549918631377eb4a74df5c043d089494dc"

     

       88
       88
       +
         ]

     

       89
       89
       +
       }

     

       90
       90
       +
       x-commit-hash: "20af6bb6e63d3120c7e1a08099dafd7a14bf8233"