Forgot to add this: > I probably could not even make a generalization about what normal closur-ing does or should look like. I would say the key reason why th

Forgot to add this: > I probably could not even make a generalization about what normal closur-ing does or should look like. I would say the key reason why this looks so wrong is that it essentially breaks lexical scope. The closures "look like" they are the same values from the scope above, but they are actually values from previous runs. I would be hard pressed to find another library API that breaks lexical scope reasoning for its closures in such a way.