Open obriencj opened 2 years ago
Work on what is tentatively called sibceval is coming along nicely! I'm unsure whether I want to merge that directly into sibilant or instead let it be its own alternative bytecode evaluator project and sibilant just targets it.
The python bytecode evaluator churns too fast, adding and removing opcodes between minor releases. While the pseudops layer of indirection worked for a while, it's too much to keep up with.
Therefore spec out and author a ceval implementation that sibilant can use for itself!