The Eff monad, one monad to rule them all
summary
Compares monad transformers to the Eff monad and claims it avoids quadratic flatMaps and keeps effect implementations independent; shows how effects are represented as a type-level union and how interpreters are composed so you can inject an S3 effect into a larger Hadoop+S3 stack. Demonstrates a Scala/Cats and Scalaz library, replaces the old action stack in specs2 successfully, notes ordering still changes semantics for state vs. error and calls for benchmarks and more production experience.
AI-written summary · about
chapters (7)
- 0:00Start
- 6:06DIFFERENCE?
- 7:39GENERALISE
- 11:18Specialized stacks
- 11:50Specialized functions
- 18:40OPTION RELOADED
- 22:38NEVER RE-IMPLEMENT
