Excise the stupid fucking `set-*` opcodes
The book uses the horribly-confusingly-named `set-*` operations for handling
subterms in query mode. The author does this because he claims this is both
easier to understand and more performant. In reality it is neither of these
things.
If you just name the subterm-handling opcodes something not completely stupid,
like `handle-subterm-*` instead of `unify-*` it becomes obvious what they do.
Also, despite the fact that `put-*` instructions now need to set the WAM's
`mode`, we still get about a 10% speedup here, likely from some combination of
reducing the VM loop code size and simplifying the compilation process. So it's
not even more performant.
TL;DR: Just say "No" to `set-*`.
| author |
Steve Losh <steve@stevelosh.com> |
| date |
Sun, 10 Jul 2016 14:21:18 +0000 |
| parents |
27f037427ad3 |
| children |
31305584b29b |
(asdf:defsystem #:bones
:name "bones"
:description "A logic programming library for Common Lisp."
:author "Steve Losh <steve@stevelosh.com>"
:maintainer "Steve Losh <steve@stevelosh.com>"
:license "MIT/X11"
:version "0.0.1"
:depends-on (#:defstar
#:optima
#:trivial-types
#:cl-arrows
#:policy-cond
#:fare-quasiquote-optima
#:fare-quasiquote-readtable)
:serial t
:components ((:file "src/quickutils") ; quickutils package ordering crap
(:file "package")
(:module "src"
:serial t
:components ((:file "paip")
(:file "utils")
(:file "circle")
(:module "wam"
:serial t
:components ((:file "constants")
(:file "types")
(:file "cells")
(:file "bytecode")
(:file "wam")
(:file "compiler")
(:file "vm")
(:file "dump")
(:file "ui")))
(:file "bones")))))