in reply to Re: i don't understand this scope behavior w/ closures and eval
in thread i don't understand this scope behavior w/ closures and eval

Nitpick: I don't think of that as just an optimization, it's necessary for garbage collection so we don't have memory leaks and destructors are executed early.

  • Comment on Re^2: i don't understand this scope behavior w/ closures and eval