News for hackers. Stuff that matters.
Re:A lambda is not necessarily a closure by thinkmoore on Tuesday February 09, 2016 @10:49AM (#11066023)
To use academic terminology, we would refer to "floating functions" as "first class functions" (since they are not second-class citizens in the language).

I would argue the true distinguishing feature of a "lambda function" in a PL is that it is first-class, nest-able, and lexically-scoped (that is, it captures bindings from its definition site).

A closure is simply a way of implementing lexical scope for functions.

A variable is a "free variable" not because it is "freed" from its lifetime, but because it is not bound by its enclosing lambda. (It would still be a free variable even if the function and the variable binding had the same lifetime.)

Re:A lambda is not necessarily a closure by rdsubhas on Tuesday February 09, 2016 @11:16AM (#11066264)
Ah dang, how I missed "first class functions" :) Thanks for reminding...