Explore >> Select a destination
|
You are here 
|
bruceeckel.com | ||
| | | | |
bartoszmilewski.com
|
|
| | | | | This is part of the book Category Theory for Programmers. The previous instalment was Category: The Essence of Composition. See the Table of Contents. The category of types and functions plays an important role in programming, so let's talk about what types are and why we need them. Who Needs Types? There seems to be... | |
| | | | |
theartofmachinery.com
|
|
| | | | | ||
| | | | |
www.jeremykun.com
|
|
| | | | | Perhaps primarily due to the prominence of monads in the Haskell programming language, programmers are often curious about category theory. Proponents of Haskell and other functional languages can put category-theoretic concepts on a pedestal or in a mexican restaurant, and their benefits can seem as mysterious as they are magical. For instance, the most common use of a monad in Haskell is to simulate the mutation of immutable data. Others include suspending and backtracking computations, and even untying tangled rope. | |
| | | | |
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. | ||
