Embracing Nondeterminism

This code accompanies a blog series covering functional programming idioms for managing nondeterminism and unknown states in production code. Please follow the series for a full explanation of the concepts represented by the code in this repository:

1. Part 1: Contexts and Effects
2. Part 2: Permitting or Halting Computation
3. Part 3: Imperative Computation

Structure of the repository

Scala packages under src/main/scala:green.thisfieldwas.embracingnondeterminism

• control contains the control-flow typeclasses such as Applicative.
• data contains commonly-used contexts that Scala defines in its own Standard Library, such as Either, List, and Option and includes Id and NonEmptyList. These code examples demonstrate different encodings of presence as the effects of operations and stand to illustrate how idioms in the series may be implemented across varying types. The Functor and Semigroup typeclasses are found here as well. data package. These exist to highlight the value in using Functor as a design pattern.

Scala packages under src/test/scala:green.thisfieldwas.embracingnondeterminism

• control contains the laws definitions for the control-flow typeclasses.
• data contains specs for each of the effect types as well as "laws" tests which assert that the associated effect type is well-defined for particular typeclasses, such as Functor.
• stdlib contains property checks to illustrate how classes in the Scala Standard Library conform to typeclass laws themselves, and highlight that you, the reader of this series, have been using some of these concepts for some time.
• util contains utility classes to aid in testing.

Using sbt console

Import all project definitions by loading the following script after launching the console:

scala> :load console/imports.scala

This will pull all classes and implicits into scope so that you can work with them directly in the console and experiment with them yourself.