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
saved by
related reading
- What is a Monad?lukechampine.com
- Abstraction, intuition, and the “monad tutorial fallacy” | blog :: Brent -> [String]byorgey.wordpress.com
- how I think when I think about programming - alice mazalicemaz.com
- combinators in Rubymooreniemi.github.io
- Reading 13: Map, Filter, Reduceweb.mit.edu
- From Imperative to Functional: how to make the leap.loup-vaillant.fr
- An introduction to functional programmingcodewords.recurse.com
- The Mondrian introduction to functional opticsmarcosh.github.io
- A practical introduction to functional programmingmaryrosecook.com
- Get better at programming by learning how things workjvns.ca
- Categories, What's the Point? || Math ∩ Programmingjeremykun.com
- Representable Functors | Bartosz Milewski's Programming Cafebartoszmilewski.com