|
That’s a really clever approach, especially the “emit a self-contained Go file” part. How did you handle jump targets and back-edge correctness without breaking more complex loops or calls?
seeing a source-level VM implementation is refreshing. How do you handle the performance overhead for those virtualized functions, and have you noticed any significant impact on the final binary size?
|