News for hackers. Stuff that matters.

A comment on Swift Functors, Applicatives, and Monads in Pictures. Parent comment

Re:Swift Functors, Applicatives, and Monads in Pictures by adamwk on Tuesday July 14, 2015 @06:19PM (#9888453)
Then why not have both? Applicative Functors have both `fmap` and `<$>`. `>>=` could easily be an alias of `flatMap` or `bind` or whatever.
[ Parent | on HN ]
Re:Swift Functors, Applicatives, and Monads in Pictures by chongli on Tuesday July 14, 2015 @06:26PM (#9888489)
I'm right there with you. I'm a Haskell user; I love user-definable operators.
[ Parent | on HN ]
Re:Swift Functors, Applicatives, and Monads in Pictures by lmm on Tuesday July 14, 2015 @07:18PM (#9888722)
Because code is read more than it's written; multiple ways of writing the same thing makes it easier to write but harder to read.
[ Parent | on HN ]
Re:Swift Functors, Applicatives, and Monads in Pictures by dragonwriter on Tuesday July 14, 2015 @07:26PM (#9888764)
Multiple ways of writing the same thing makes it easier to read, often, because you are more free to use the form that is more readable and intuitive in context; that's one reason why natural languages (including written languages) tend to have multiple ways of expressing the same ideas.
[ Parent | on HN ]