I really look forward to reading the book myself, and don't have a background in compilation, but will probably try using my own language of choice for the firs

I really look forward to reading the book myself, and don't have a background in compilation, but will probably try using my own language of choice for the first half anyways, because I feel I know what I want and no one can stop me :p > Second, because it's so large and packed already, the author left quite a few things out, particularly testing. There's precious little actual Lox code in the book, and no testing strategy. Testing interpreters well is relatively easy and very powerful, especially when implementing multiple ones for the same language. I do understand the space constraints, however. It's worth mentioning that the author does have a repo containing the tests they used while creating the book, which can be ran against the state of each interpreters (including your own) at the end of each chapter, which is really cool: https://github.com/munificent/craftinginterpreters#testing-your-implementation https://github.com/munificent/craftinginterpreters#testing-y...