pub fn vm_listing(input: &str) -> Result<String, String>Expand description
The bytecode the VM runs for input, as largo run --interpret compiles it: the run path’s optimizer, the oracle
and the VM compiler. One section per function, ## Main first, then ## To <name> in code order, each instruction
at its pc. A source that does not parse, or that only the tree-walker runs, answers why.