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...
Re:A lambda is not necessarily a closure
by theseoafs on Tuesday February 09, 2016 @11:16AM
(#11066261)
> Lambda functions: A style of writing functions without a block, where the function and return value are expressed as one single expression without the usage of a block or explicit returns.
employee => employee.name
This is not what a lambda is.
Floating Functions / First class functions (thanks to comments for reminding): Functions that can be passed around as variables. e.g. All functions in Javascript are floating functions.
Anonymous functions: functions with no name. Lambda functions: A style of writing functions without a block, where the function and return value are expressed as one single expression without the usage of a block or explicit returns. Closures: When a function references a variable outside its scope, and that "frees" the variable from its normal lifetime, thus creating a "closure" between the function and the now-free variable.