I actually kind of disagree. map(f).getOrElse(y) clearly conveys the intent of your code and makes it easy to understand for other people. fold(y)(f) doesn't. In my case at least, I always have to do the mental gymnastic of "oh, this means map.getOrElse"
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Ah. So then, on the one hand it makes sense, on the other, I feel it might be a fact in favour of my argument: it might be unreasonable (today) to expect most developers to know about algebraic folds, and map(x).getOrElse(y) *will* be more readable for the majority of them
Why is it unreasonable to expect developers to know the basics of their profession? Is it also unreasonable to expect pilots to not know where the throttle is located?
-
-
This Tweet is unavailable.
-
The practical consequences for not understanding the basics in programming are just as dire, but less direct.
- Show replies
-
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.