Bill Tozier
Bill Tozier
given the first-class nature of both Router and Recognizer items, consider a set of "peek" and "yank" combinators based on pattern-matching. For example, `:code-matching` might peek/yank the first item matching...
Based on #175: Consider also revising `:vectorizable` to construct items in this same way. That is, rather than there being an independent vector-of-thing type for each type, consider making a...
For promiscuous routing, need to have a type hierarchy or Venn diagram
Heh. I just wanted to type ":type type". Well, no. But the big question is whether these should be keywords (again!?) or a Clojure record. I'd guess a record. Otherwise...
There needs to be some adjustment made to `push.instructions.core/needs-of-dsl-step` and `products-of-dsl-step`. The `0` values are no longer necessary (although I suppose there should be checks on `push-onto` that automatically produce...
take their `:transaction` steps and concatenate them, producing a new consolidated function on the fly. For example, `(:scalar-add 9 :boolean-or :scalar-≤)` ```text (consume-top-of :scalar :as :arg2) (consume-top-of :scalar :as :arg1)...
It will be easiest to set up an interpreter's ontology (bindings, instructions, types etc that it recognizes) using something like this (extended from the templates): - start with a template...
instead of the target stacks, or perhaps new instructions that send items to `:snapshot` as such
# Type handling in Klapaucius (a reconciliation; also a draft) All items that appear in Push code (including Push programs and code blocks) are _strictly typed_. This affects the interpreter's...
When an interpreter runs a program, it should be possible to return one of several useful values/types, plus information on how it was set up. - program ID - program...