Why not... you could "just" during compilation split it into several functions and daisy-chain them if it came to that, by letting one calling the other with wh

Why not... you could "just" during compilation split it into several functions and daisy-chain them if it came to that, by letting one calling the other with whatever state is needed to transfer. I'd bet it could even be part of a simple optimization pass. Single assign semantics help with eliminating useless scope and all that.