Function.IDENTITY and Function.EMPTY are never called directly,
though. They're canonical functions.
Agreed. Hence, Function.reference instead of Function.empty.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Are you sure not Function.eMpTy ?
:P
---
Warm Regards,
Ryan Gahl
On Fri, Oct 16, 2009 at 6:15 AM, Joran Greef jorangr...@gmail.com wrote:
Function.IDENTITY and Function.EMPTY are never called directly,
though. They're canonical functions.
Agreed. Hence, Function.reference instead of
On Oct 16, 9:14 am, Ryan Gahl ryan.g...@gmail.com wrote:
Are you sure not Function.eMpTy ?
Would the order of capitalization be based on phase of the moon?
[...]
--
kangax
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Hi, Andrew.
As previously mentioned, K is ambiguous, as it can mean both:
function K(arg) { return arg; }
or:
function K(arg) { return function() { return arg; }; }
depending on your reference (Tcl for the former, combinatory logic for
the latter).
My vote therefore goes for using
Don't get me wrong, but we are not talking about splitting the core of the
atom in 16 different particles. Instead the topic of discussion is how to
name (and where to place) the empty and identity function.
Two things should be taken into account -- common sense and consistency.
Deriving from
Extends your Prototype, the Force does, mnn...
---
Warm Regards,
Ryan Gahl
On Fri, Oct 16, 2009 at 4:48 PM, joneff jon...@gmail.com wrote:
(off topic, or would it be May the Force extends your.prototype?)
--~--~-~--~~~---~--~~
You received this
