Picks the ASP backend per solve: in-process clingo (vaelii.impl.asp.clingo, resolved
on first use so JNA stays optional) or the clasp subprocess. asp.edge, asp.label and
asp.solve-context call solve, classify-both and available?. See docs/asp.md,
"Getting a solver".
Picks the ASP backend per solve: in-process clingo (`vaelii.impl.asp.clingo`, resolved on first use so JNA stays optional) or the clasp subprocess. `asp.edge`, `asp.label` and `asp.solve-context` call `solve`, `classify-both` and `available?`. See docs/asp.md, "Getting a solver".
(available?)True if the selected backend can solve in this environment. The clasp answer is the once-per-JVM probe routing reads.
True if the selected backend can solve in this environment. The clasp answer is the once-per-JVM probe routing reads.
(classify-both aspif-text)The cautious and the brave enumeration of aspif-text: {:cautious <result> :brave <result>}, each shaped like solve. clingo loads the program once for both; clasp runs
two solves.
The cautious and the brave enumeration of `aspif-text`: `{:cautious <result> :brave
<result>}`, each shaped like `solve`. clingo loads the program once for both; clasp runs
two solves.(solve program mode)Solve translated program {:aspif <text> :stmts <statements>} in mode on the backend
backend-for picks by the ASPIF byte length, returning the shape clasp/solve and
clingo/solve share. clingo reads :stmts, clasp the :aspif text.
Solve translated program `{:aspif <text> :stmts <statements>}` in `mode` on the backend
`backend-for` picks by the ASPIF byte length, returning the shape `clasp/solve` and
`clingo/solve` share. clingo reads `:stmts`, clasp the `:aspif` text.cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |