✳flâneur — a map of the web's best reading
Monoids without tears | F# for fun and profit
fsharpforfunandprofit.com · 3,841 words · saved by 1 readers
A mostly mathless discussion of a common functional pattern
If you are coming from an OO background, one of the more challenging aspects of learning functional programming is the lack of obvious design patterns. There are plenty of idioms such as partial application , and error handling techniques , but no apparent patterns in the GoF sense . In this post, we'll look at a very common "pattern" known as a monoid . Monoids are not really a design pattern; more an approach to working with many different types of values in a common way. In fact, once you understand monoids, you will start seeing them everywhere! Unfortunately the term "monoid" itself is a
Explore this link on the map →saved by
related reading
- What is a Monad?lukechampine.com
- Abstraction, intuition, and the “monad tutorial fallacy” | blog :: Brent -> [String]byorgey.wordpress.com
- Typeclassopedia - HaskellWikiwiki.haskell.org
- Category Theory on Math3mamath3ma.com
- How Sridhar Thinkssridharramesh.github.io
- CSC 151 - The "big three" list operationseikmeier.sites.grinnell.edu
- CSC 151 - Higher-order design, recursive and othereikmeier.sites.grinnell.edu
- Bartosz Milewski's Programming Cafe | Category Theory, Haskell, Concurrency, C++bartoszmilewski.com
- A practical introduction to functional programmingmaryrosecook.com
- Reading 13: Map, Filter, Reduceweb.mit.edu
- magma in nLabncatlab.org
- Radimentary | "Everything can be made radically elementary." ~Steven Rudichradimentary.wordpress.com