Bill Tozier

I notice a lot of the instruction names are pretty long. Can I get away with renaming them `enum_thingie` rather than `enumerator_thingie`, or is the naming standard to always use...

Quick judgment call: Should instructions like `enumerator_map_code` leave the `code` item in place on that stack after they've exhausted the `enumerator`, or pop it?

That makes sense, and confirms my expectations. So what it's doing now is leaving a copy of the top `:code` item until it deletes itself. This permits the same kind...

What C calls `enum` I would call `categorical` if I were to import my types to handle small symbolic sets....

Oh no, I can guarantee a much higher level of confusion, just by pointing out that Clojure permits Unicode function names.... ``` clojure clojush.core=> (defn ℤ⊕ [a b] (+ a...

$$c log(c)$$

OK, I _think_ I have things squared away. In order to get a minimal viable set in folks' hands, I did not implement some tricky and odd things - `enumerator_from_code`...

(that said, I am just now about to do a run with this stuff turned on, so... soon) **Later:** Yeah, no; I'm going to need some explicit help from somebody...

@thelmuth - facepalm; no I didn't ever add `emulator_emit` (and `pos`) to my lists, because it was obvious... so I totally forgot about it - `map` is pretty difficult to...

@thelmuth Let's talk more about proper `map` and other functional instructions. Here are the things I can determine, thinking about the instruction set we have already: For numeric `vector` types,...