This looks real cool, and the logic behind treating OpenSCAD files this way in a 3d printing workflow is impeccable.

I stumbled at first because all my scad files use language features not supported in hob3l. It might help to call more attention to the .scad → (openscad) → .csg → (hob3l) workflow.

Blew right past my notebook's 8GB RAM trying to slice a complex fractal model at 6 levels of recursion. This is a "favorite" model of mine because I've never gotten openscad to slice it right: https://emergent.unpythonic.net/files/sandbox/flake6.csg.gz

Slicing level 5 only took about 4GB RAM so maybe level 6 needs around 24? https://emergent.unpythonic.net/files/sandbox/flake5.csg.gz