The generation of the diagrams for the user manual requires a lot of manual work: trigger the generation and copying the graphs into the right directory. This generation process needs to be unified and automated. Ideally one script call, e.g. generate_graphs.sh, should trigger the generation process and copy the results into the correct directory.

The place where the diagram generation code i

I was upgrading some dev stuff on my laptop, and did the obvious-seeming thing in the Clojush folder: lein run. (autocorrect doesn't like lein)

I think probably instead of an exception (because I didn't specify any args), it should return a cleaned-up directory tree of the problems directory, with instructions how to run any individual demo.

The packed_t is used to pack bits together. However, it seems that perhaps std::bitset might do this better, and also offer more features, functions, etc. It might simplify the code!? and might? run faster?

The Optimizers must all be present in buildOptions for a successful build.
Should be documented (and more clearly named) if this is the correct behavior.

I am noticing instructions like _exec_empty cropping up quite a lot. I realize that in Python variable names can only include underscores and Alnum characters, but I wonder if it might make Push code a bit more readable to name these in the Mathematica style: ending in Q (indicating "question", I guess?).

So for example _exec_empty_Q.

Just a minor suggestion. In Clojure implementatio

47:15-28 Critical dependency: the request of a dependency is an expression
 @ ./common/src/plugins/Plugins.js
 @ ./client/src/manager/Plugins.js
 @ ./client/src/manager/Manager.js
 @ ./client/src/App.js

WARNING in ./node_modules/ws/lib/BufferUtil.js
Module not found: Error: Can't resolve 'bufferutil' in 'C:\db\projects\jevo.js\node_modules\ws\