Re:The Wrong Aesthetic
by loup-vaillant on Sunday June 13, 2010 @01:11PM
(#1427727)
> I suspect those that have seen map, inject, and their ilk wouldn't be so confused.
No doubt. However, C++ stays a major contributor to that confusion. In ML languages,
let total = foldl (+) 1 (map face_value dice)
is nearly idiomatic. Compare that to the C++ code. Compare that to C++ code that would use accumulate and an equivalent of map.I don't disagree. But it's a weakness of C++, not of the language concept itself.
Perhaps if OP was saying you shouldn't use it for C++, then maybe I'd say he'd have a case.
> Perhaps if OP was saying you shouldn't use it for C++
I think that's exactly what he was saying.
Re:The Wrong Aesthetic
by loup-vaillant on Sunday June 13, 2010 @06:06PM
(#1428299)
It is.
Ah. I didn't get that from reading it.
And in Haskell,
foldl (+) 1 (map face_value dice)
would use fusion to avoid causing map to create another array!Incidentally fusion won't work for this example (at least not as currently implemented.) Only `foldr` is fusable. Fortunately, regular inlining does just fine.
There is of course an even simpler version:
sum (map face_value dice)Why does the sum start with 1? Why not eg.
foldl1' (+) $ map face_value dice
Re:The Wrong Aesthetic
by loup-vaillant on Sunday June 13, 2010 @06:10PM
(#1428307)
It should have started with 0. Sorry. And I avoided `foldl1` because I wanted to stay close to C++'s `accumulate`.
Shouldn't that be:
let total = foldl (+) 0 (map face_value dice)
Re:The Wrong Aesthetic
by loup-vaillant on Sunday June 13, 2010 @06:08PM
(#1428304)
Whoops. Yes it should.
http://news.ycombinator.com/item?id=1358753
Sometimes, things are confusing or are seemingly super weird depending on your background. While I haven't done C++ in years, I recognized that std::accumulate() was probably very much like Ruby's inject().
I suspect those that have seen map, inject, and their ilk wouldn't be so confused.
While you can argue that the 'average corporate programmer' wouldn't know what the hell it is, and you might be right. But if we stuck with that attitude, we'd still be using goto's liberally because the 'average corporate programmer' would find for loops weird and confusing.