The purpose of this extension was not really to aid in writing Feeny. It was more about aiding getting through the course. One thing that's kind of a pain is dealing with bytecode files.

Eventually I wrote a small utility script that just reads a bytecode file and runs print_prog on it. It would be nice if I could get the output of print_prog in the editor as a first step, perhaps through a virtual buffer.

Still, the output of print_prog is not very human-readable. You end up having to jump back-and-forth between a method's calls and the value table. It would be nice if the editor could use something like inlay hints to preview values and labels easily. Go to definition would be nice too. Errors could help validate whether code in lab4 is valid without having to run the VM every time.