/explore
|
You are here 
|
diego.codes | ||
| | | | |
mmhaskell.com
Monads are viewed as one of the harder topics to learn in Haskell. But they don't have to be. Learn monads the easy way, by first looking at other functional structures like functors and applicatives. |
|
| | | | | ||
| | | | |
kndrck.co
Prelude State monads, introduced to me during the data61 functional programming course was one of my most memorable encounter with a monad. This was mainly because things only started to clicked and made a tiny bit of sense after a couple of weeks of frustration. This article is my attempt to explain the underlying mechanics of the State Monad to try and relief the frustration of whomever who was in my position. |
|
| | | | | ||
| | | | |
www.stephendiehl.com
|
|
| | | | | ||
| | | | |
www.jeremykun.com
A lot of people who like functional programming often give the reason that the functional style is simply more elegant than the imperative style. When compelled or inspired to explain (as I did in my old post, How I Learned to Love Functional Programming), they often point to the three "higher-order" functions map, fold, and filter, as providing a unifying framework for writing and reasoning about programs. But how unifying are they, really? |
|
| | | |||
