News for hackers. Stuff that matters.
Re:How currying leads to elegant, readable code by skybrian on Thursday June 19, 2014 @05:31PM (#7918420)
Well, avoiding mutation can be helpful but it's not a rule to be followed blindly either. A mutable local variable never hurt anyone, so long as it doesn't leak out of the function.
Re:How currying leads to elegant, readable code by daemonize on Friday June 20, 2014 @12:34AM (#7919535)
Even in a multiple-thread scenario?
Re:How currying leads to elegant, readable code by twic on Friday June 20, 2014 @07:06AM (#7920232)
As an aside, one of the really interesting ideas that's bubbling up from Rust is that it's not mutable state that's a problem, it's shared mutable state, and that you can make it safe by removing the sharing, rather than removing the mutability:

http://smallcultfollowing.com/babysteps/blog/2014/05/13/focu...

I have no idea if this is true, but it's going to be really interesting to see that idea tried.

Re:How currying leads to elegant, readable code by skybrian on Friday June 20, 2014 @01:54AM (#7919660)
If it doesn't leak out of the function (though a closure or a pointer), how can another thread see it? It's only on one stack.