Re:A lambda is not necessarily a closure
by nailer on Tuesday February 09, 2016 @05:58AM
(#11064517)
Swift even does this officially: ALL lambdas are called closures, even though there's nothing being closed over.
Similarly, people refer to constructor functions that always return objects of the same class/prototype as factories, despite both the GoF patterns that popularised the term showing dynamic output. IIRC Angular JS misuses the term this way too.
AFAICT it's either genuine ignorance of how/why these words describe or some kind of weird demonstration of cleverness by using a particular term, regardless of whether it's applicable or not.
Re:A lambda is not necessarily a closure
by Ono-Sendai on Tuesday February 09, 2016 @07:27AM
(#11064801)
It's probably because, in an implementation of a staticly typed language, you have to treat all functions being passed around as closures. E.g. the type of a lambda expression needs to be one thing, and that is a closure.
Whether or not any variables are actually closed over is irrelevant.
Re:A lambda is not necessarily a closure
by nailer on Tuesday February 09, 2016 @10:18AM
(#11065801)
Couldn't the type of a passed around function simply be 'function'? Why does it have to be inaccurate?
Re:A lambda is not necessarily a closure
by Ono-Sendai on Tuesday February 09, 2016 @12:17PM
(#11066879)
Well a function may in general have closed over arguments. Therefore it needs to be a closure. (If you have lexical scoping that is)
I'm not overly fond of calling anonymous functions "lambdas", for that matter. Sure, several languages use the term lambda, but many do not. More specifically, "anonymous function" is much more descriptive than "lambda".