wow, I had no idea. should I implement this behaviour in pulp-to-lua...?
Edit: wow! It turns out a whole bunch of games like this platformer and others critically rely on this behaviour. This is because goto also immediately triggers an update to occur, and then e.g. event.dy == -1 gates behaviour that would cause another goto, and so a stack overflow would occur if event.dx/event.dy hadn't changed. I had nearly given up on trying to figure out why these stack overflows were occurring. Thank you for the report! Hmm!