stouset is obviously not arguing that the ruby version with "&:" is immediately obvious to any programmer. The point is if you know ruby, you will understand that line a lot quicker than the second example.
[1, 2, 3, 4, 5].reduce(0, &:+) #=> 15
Which is short hand for: [1, 2, 3, 4, 5].reduce(0) { |memo, item| memo + item } #=> 15[1, 2, 3, 4, 5].reduce(:+)
[1,2,3].reduce([], &:unshift) #=> [3,2,1]
I don't see a problem with writing a for loop, but I think it's not as composable and it can be a little harder to read. So I don't think it's purely religious but it's close to that. inserts :: [(VarId,VarId)] -> Env -> Env
inserts vvs env = foldr (\(a,b) acc -> M.insert a b acc) env vvs
or inserts(vvs, env) {
for ((a, b) : vvs) {
env = M.insert(a, b, env)
}
return env
}
Pick your poison, but I'll stick with fors. Go blues! vvs.reduce(env){|env, (a,b)| M.insert(a, b, env)}
but the for loop is perfectly readable also because it fits on a single line. I think for longer bodied reduces I might prefer a for loop actually.