A Skeptic’s Guide to Scalaz’ Gateway Drugs: Part 1 - Disjunctions

| Comments

(This is Part 1 of a series of distillations of a presentation I’ve been giving for the last year, “A Skeptic’s Guide to scalaz’ Gateway Drugs”. It is meant to provide an introduction to the core functionality of scalaz that a developer might find most useful, without going off the deep end.)

What is scalaz exactly? Well, at its core, scalaz is a functional programming library for Scala. It is intended to bring more functional programming concepts from languages like Haskell into Scala.

Until recently, I’ve looked at scalaz rather skeptically. As a self taught developer without any college or advanced mathematics training, I felt intimidated by what I saw. Long before I exited the ranks of rookie Scala programmer, I dabbled in Haskell a bit but left more confused than I started at.

So, tools like scalaz were a bit scary to me. Plus, “what’s wrong with the Scala standard library?”. As it turns out, a lot. Let’s look first at Scala’s Either, and where we can improve upon it. Scala’s builtin Either is a common construct used to indicate one of two conditions: Success or Error. These are, by convention, Left for Errors, and Right for Success. The concept is good, but there are some limits to interaction. By default, we cannot use it in a for comprehension:

 1 scala> val success = Right("Success!")
 2 success: scala.util.Right[Nothing,String] = Right(Success!)
 4 scala> success.isRight
 5 res2: Boolean = true
 7 scala> success.isLeft
 8 res3: Boolean = false
10 scala> for {
11        |   x <- success
12        | } yield x
13        <console>:10: error: value map is not a member of scala.util.Right[Nothing,String]
14                       x <- success
15                            ^

(Note, there is a function called rightProjection which converts an Either into something comprehendable)

In the scalaz world, there is a similar construct to Either, known as \/. If \/ reads like a mouthful, you can call it Disjunction - which we’ll do in this post as well. A Disjunction can, like in Either have either a Left or a Right side - typically representative of a Success (right) or an Error (left). These are represented by symbols: -\/ for Left, \/- for Right.

(I find, in general, that the easiest memory trick is to look at which side of the Disjunction the - appears on.)

With Disjunctions, there is an assumption that we prefer Success (the right, or \/-) - this is also known as Right Bias. With Right Bias, for comprehensions, map, and flatMap unpack for us where “success” (\/-) continues and “failure” (-\/) aborts.

When declaring a return type of a Disjunction, you should generally prefer to use the Infix notation for clarity sake. That is to say:

1 def query(arg: String): Error \/ Success

with the Infix notation for the return type, is preferable to this:

1 def query(arg: String): \/[Error, Success]

the standard notation, which may not read as clearly.

As for declaring instances of Left or Right, there are a few options in scalaz. The first is postfix operators, .left and .right, which wrap an existing value in a Disjunction instance:

1 import scalaz._
2 import Scalaz._
4 scala> "Success!".right
5 res7: scalaz.\/[Nothing,String] = \/-(Success!)
7 scala> "Failure!".left
8 res8: scalaz.\/[String,Nothing] = -\/(Failure!)

Alternately, we can use the Disjunction singleton instance instead:

1 import scalaz._
2 import Scalaz._
4 scala> \/.left("Failure!")
5 res10: scalaz.\/[String,Nothing] = -\/(Failure!)
8 scala> \/.right("Success!")
9 res12: scalaz.\/[Nothing,String] = \/-(Success!)

which, by virtue of being more explicit, may be clearer to the reader.

Finally, we can construct instances of Left and Right directly:

1 import scalaz._
2 import Scalaz._
4 scala> -\/("Failure!")
5 res9: scalaz.-\/[String] = -\/(Failure!)
7 scala> \/-("Success!")
8 res11: scalaz.\/-[String] = \/-(Success!)

Remember I talked about how we could comprehend over Disjunctions, and success continued while failure aborted?

Here's Johnny?

Let’s look at what that looks like with some sample data:

 1 import scalaz._
 2 import Scalaz._
 4 val success1 = \/.right("This succeeded")
 6 val success2 = \/.right("This succeeded also!")
 8 val fail1 = \/.left("This failed miserably...")
10 val fail2 = \/.left("Oops :(")

We now have a couple of Disjunction instances we can use. If we comprehend over only Right, we get back an instance of Right.

1 for {
2   one <- success1
3   two <- success2 
4 } yield (one, two)
5 /* res0: scalaz.\/[Nothing,(String, String)] = 
6       \/-((This succeeded,This succeeded also!)) */

Since both instances we used were Right, we get back an instance of Right ( \/- ).

What if we include a Left in there?

1 for {
2   one <- success1
3   two <- fail1  
4   three <- success2
5 } yield (one, three)
6 /* res1: scalaz.\/[String,(String, String)] = 
7       -\/(This failed miserably...) */

The behavior here is much like with an Option instance of None (Which we’ll talk about in the next post). When Scala encounters a “failure” - in this case a Left ( -\/ ) - it aborts the iteration and returns an instance of the failure. This case means the yield never gets run. This can be valuable as an easy way to work with multiple Disjunctions all of which needed to be Right.

Now you’ve had a (hopefully) gentle introduction to the world of \/. In the next part, we’ll talk about using Scala’s Option in conjunction with Disjunctions to better handle failure conditions with existing code.