Scryer Prolog

Scryer Prolog aims to become to ISO Prolog what GHC is to Haskell: an open source industrial strength production environment that is also a testbed for bleeding edge research in logic and constraint programming, which is itself written in a high-level language.

Phase 1

Produce an implementation of the Warren Abstract Machine in Rust, done according to the progression of languages in Warren's Abstract Machine: A Tutorial Reconstruction.

Phase 1 has been completed in that Scryer Prolog implements in some form all of the WAM book, including lists, cuts, Debray allocation, first argument indexing, last call optimization and conjunctive queries.

Phase 2

Extend Scryer Prolog to include the following, among other features:

Phase 3

Use the WAM code produced by the completed code generator to get JIT-compiled and -executed Prolog programs. The question of how to get assembly from WAM code is something I'm still considering.

It's my hope to use Scryer Prolog as the logic engine of a low level (and ideally, very fast) Shen implementation.

Nice to have features

There are no current plans to implement any of these, but they might be nice to have in the future. They'd make a good project for anyone wanting to contribute code to Scryer Prolog.

  1. Implement the global analysis techniques described in Peter van Roy's thesis, "Can Logic Programming Execute as Fast as Imperative Programming?"

  2. Add unum representation and arithmetic, using either an existing unum implementation or an ad hoc one. Unums are described in Gustafson's book "The End of Error."

  3. Add concurrent tables to manage shared references to atoms and strings.

  4. Add some form of JIT predicate indexing.

Installing Scryer Prolog

First, install the latest stable version of Rust using your preferred method. Scryer tends to use features from newer Rust releases, whereas Rust packages in Linux distributions, Macports, etc. tend to lag behind. rustup will keep your Rust updated to the latest stable release; any existing Rust distribution should be uninstalled from your system before rustup is used.

Scryer Prolog can be installed with cargo, like so:

$> cargo install scryer-prolog

cargo will download and install the libraries Scryer Prolog uses automatically from crates.io. You can find the scryer-prolog executable in ~/.cargo/bin.

Publishing Rust crates to crates.io and pushing to git are entirely distinct, independent processes, so to be sure you have the latest commit, it is recommended to clone directly from this git repository, which can be done as follows:

$> git clone https://github.com/mthom/scryer-prolog $> cd scryer-prolog $> cargo run [--release]

The optional --release flag will perform various optimizations, producing a faster executable.

Tutorial

To enter a multi-clause predicate, the directive "[user]" is used.

For example, ?- [user]. (type Enter + Ctrl-D to terminate the stream when finished) p(f(f(X)), h(W), Y) :- g(W), h(W), f(X). p(X, Y, Z) :- h(Y), z(Z). ?- [user]. (type Enter + Ctrl-D to terminate the stream when finished) h(x). h(y). h(z). In the example, Enter + Ctrl-D is used to terminate the standard input stream. The instructive message is always printed.

Queries are issued as ?- p(X, Y, Z).

Pressing SPACE will backtrack through other possible answers, if any exist. Pressing . will abort the search and return to the prompt.

Wildcards work as well:

?- [user]. (type Enter + Ctrl-D to terminate the stream when finished) member(X, [X|_]). member(X, [_|Xs]) :- member(X, Xs). ?- member(X, [a, b, c]). X = a ; X = b ; X = c ; false. and so do conjunctive queries: ?- [user]. (type Enter + Ctrl-D to terminate the stream when finished) f(X) :- g(X). g(x). g(y). g(z). h(call(f, X)). ?- h(X), X. X = call(f,x) ; X = call(f,y) ; X = call(f,z).

Note that the values of variables belonging to successful queries are printed out, on one line each. Uninstantiated variables are denoted by a number preceded by an underscore (X = _0 in an example above).

To quit scryer-prolog, type ?- halt.

Dynamic operators

Scryer supports dynamic operators. Using the built-in arithmetic operators with the usual precedences,

?- write_canonical(-5 + 3 - (2 * 4) // 8), nl. -(+(-5,3),//(*(2,4),8)) true.

New operators can be defined using the op declaration.

Strings and partial strings

In Scryer Prolog, the default value of the Prolog flag double_quotes is chars, which is also the recommended setting. This means that double-quoted strings are interpreted as lists of characters, in the tradition of Marseille Prolog.

For example, the following query succeeds:

?- "abc" = [a,b,c]. true.

Internally, strings are represented very compactly in packed UTF-8 encoding. A naive representation of strings as lists of characters would use one memory cell per character, one memory cell per list constructor, and one memory cell for each tail that occurs in the list. Since one memory cell takes 8 bytes on 64-bit machines, the packed representation used by Scryer Prolog yields an up to 24-fold reduction of memory usage, and corresponding reduction of memory accesses when creating and processing strings.

Scryer Prolog uses the same efficient encoding for partial strings, which appear to Prolog code as partial lists of characters. The predicate partial_string/3 from library(iso_ext) lets you construct partial strings explicitly. For example:

?- partial_string("abc", Ls0, Ls). Ls0 = [a,b,c|Ls].

In this case, and as the answer illustrates, Ls0 is indistinguishable from a partial list with tail Ls, while the efficient packed representation is used internally.

An important design goal of Scryer Prolog is to automatically use the efficient string representation whenever possible. Therefore, it is only very rarely necessary to use partial_string/3 explicitly. In the above example, posting Ls0 = [a,b,c|Ls] yields the exact same internal representation, and has the advantage that only the standard predicate (=)/2 is used.

Definite clause grammars as provided by library(dcgs) are ideally suited for reasoning about strings.

Modules

Scryer has a simple predicate-based module system. It provides a way to separate units of code into distinct namespaces, for both predicates and operators. See the files src/prolog/lib/*.pl for examples.

At the time of this writing, many predicates reside in their own modules that need to be imported before they can be used. The modules that ship with Scryer Prolog are also called library modules or libraries, and include:

To use predicates provided by the lists library, write:

?- use_module(library(lists)).

To load modules contained in files, the library functor can be omitted, prompting Scryer to search for the file (specified as an atom) from its working directory:

?- use_module('file.pl').

use_module directives can be qualified by adding a list of imports:

?- use_module(library(lists), [member/2]).

A qualified use_module can be used to remove imports from the toplevel by calling it with an empty import list.

The (:)/2 operator resolves calls to predicates that might not be imported to the current working namespace:

?- lists:member(X, Xs).

The [user] prompt can also be used to define modules inline at the REPL:

``` ?- [user]. (type Enter + Ctrl-D to terminate the stream when finished) :- module(test, [localmember/2]). :- usemodule(library(lists)).

local_member(X, Xs) :- member(X, Xs). ```

The user listing can also be terminated by placing end_of_file. at the end of the stream.