Re:Why Swift Guard Should Be Avoided
by alexjarvis on Saturday January 02, 2016 @06:25AM
(#10825874)
Yes it's more cognitive overhead but it's a more functional than imperative style which usually has many advantages. If the functions are named well (naming being the hardest problem) then it should be easy to read without knowing exactly what the implementation of the function does.
[ Parent
| on HN ]
Re:Why Swift Guard Should Be Avoided
by Dylan16807 on Saturday January 02, 2016 @07:37AM
(#10826015)
I fail to see how reduceDepositedCoinsBy is in any way more functional.