@RonJeffries @bitemyapp @kragen @marick Consider that in OO, all methods are just curried functions with `self` being captured.
-
-
Replying to @sgrif
@sgrif@RonJeffries@kragen@marick I can't think of any OO languages with curried methods.2 replies 0 retweets 0 likes -
Replying to @bitemyapp
@bitemyapp If you mean explicit user facing currying, and not the ideological aspect I'm talking about, Scala has it1 reply 0 retweets 0 likes -
Replying to @sgrif
@sgrif I'm not sure what ideology has to do with PL. Ideology is normative and usually concerns political science.1 reply 0 retweets 0 likes -
Replying to @bitemyapp
@sgrif there's really only one kind of currying: Eschewing multi-arg functions (tupled or otherwise) in favor of nested unary functions.2 replies 0 retweets 0 likes -
Replying to @bitemyapp
@bitemyapp How is http://MyObject.new (foo).call(bar) fundamentally different? (Assuming immutability)1 reply 0 retweets 0 likes -
Replying to @sgrif
@sgrif phew, okay, I see what you're getting at now. That's still not currying though.2 replies 0 retweets 0 likes -
Replying to @bitemyapp
@sgrif method chaining is something else and rarely has anything like nested functions, function application, or lexical scope involved.1 reply 0 retweets 0 likes -
Replying to @bitemyapp
@bitemyapp Any language with inner classes is certainly has lexical scope and nested functions. See for example Java 8 lambdas.1 reply 0 retweets 0 likes -
Replying to @sgrif2 replies 0 retweets 0 likes
@bitemyapp I like that you've argued with two people now assuming we don't know what currying is. I write Haskell. I'm not an idiot.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.