Seamless interop layer between cats and scalaz
Clone or download

shims Build Status Gitter Latest version

Shims aims to provide a convenient, bidirectional, and transparent set of conversions between scalaz and cats, covering typeclasses (e.g. Monad) and data types (e.g. \/). By that I mean, with shims, anything that has a cats.Functor instance also has a scalaz.Functor instance, and vice versa. Additionally, every convertible scalaz datatype – such as scalaz.State – has an implicitly-added asCats function, while every convertible cats datatype – such as – has an implicitly-added asScalaz function.

Only a single import is required to enable any and all functionality:

import shims._

Toss that at the top of any files which need to work with APIs written in terms of both frameworks, and everything should behave seamlessly. You can see some examples of this in the test suite, where we run the cats laws-based property tests on scalaz instances of various typeclasses.


Add the following to your SBT configuration:

libraryDependencies += "com.codecommit" %% "shims" % "<version>"

If you're using scala.js, use %%% instead. Cross-builds are available for Scala 2.11 and 2.12. It is strongly recommended that you enable the relevant SI-2712 fix in your build. Details here. A large number of conversions will simply not work without partial unification.

Once you have the dependency installed, simply add the following import to any scopes which require cats-scalaz interop:

import shims._

Chuckle… there is no step three!

Effect Types

You can also use shims to bridge the gap between the older scalaz Task hierarchy and newer frameworks which assume cats-effect typeclasses and similar:

libraryDependencies += "com.codecommit" %% "shims-effect" % "<version>"
import shims.effect._

For more information, see the shims-effect subproject readme.

Upstream Dependencies

  • cats 1.1.0
    • Note: cats 1.0.x is binary-compatible with 1.1.0, so the eviction should be safe
  • scalaz 7.2.24

At present, there is no complex build matrix of craziness to provide support for other major versions of each library. This will probably come in time, when I've become sad and jaded, and possibly when I have received a pull request for it.

Quick Example

In this example, we build a data structure using both scalaz's IList and cats' Eval, and then we use the cats Traverse implicit syntax, which necessitates performing multiple transparent conversions. Then, at the end, we convert the cats Eval into a scalaz Trampoline using the explicit asScalaz converter.

import shims._

import cats.Eval
import cats.syntax.traverse._
import scalaz.{IList, Trampoline}

val example: IList[Eval[Int]] = IList(,,

val sequenced: Eval[IList[Int]] = example.sequence
val converted: Trampoline[IList[Int]] = sequenced.asScalaz



Typeclass conversions are transparent, meaning that they will materialize fully implicitly without any syntactic interaction. Effectively, this means that all cats monads are scalaz monads and vice versa.

What follows is an alphabetized list (in terms of cats types) of typeclasses which are bidirectionally converted. In all cases except where noted, the conversion is exactly as trivial as it seems.

  • Applicative
  • Apply
  • Arrow
  • Choice
    • Requires a Bifunctor[F] in addition to a Choice[F]. This is because scalaz produces a A \/ B, while cats produces an Either[A, B].
  • Bifoldable
  • Bifunctor
  • Bitraverse
  • Category
  • Choice
  • CoflatMap
  • Comonad
  • Compose
  • Contravariant
  • Eq
  • FlatMap
    • Requires Bind[F] and either BindRec[F] or Applicative[F]. This is because the cats equivalent of scalaz.Bind is actually scalaz.BindRec. If an instance of BindRec is visible, it will be used to implement the tailRecM function. Otherwise, a stack-unsafe tailRecM will be implemented in terms of flatMap and point.
    • The cats → scalaz conversion materializes scalaz.BindRec; there is no conversion which just materializes Bind.
  • Foldable
  • Functor
  • InjectK
    • This conversion is weird, because we can materialize a cats.InjectK given a scalaz.Inject, but we cannot go in the other direction because scalaz.Inject is sealed.
  • Invariant (functor)
  • Monad
    • Requires Monad[F] and optionally BindRec[F]. Similar to FlatMap, this is because cats.Monad constrains F to define a tailRecM function, which may or may not be available on an arbitrary scalaz.Monad. If BindRec[F] is available, it will be used to implement tailRecM. Otherwise, a stack-unsafe tailRecM will be implemented in terms of flatMap and point.
    • The cats → scalaz conversion materializes scalaz.Monad[F] with scalaz.BindRec[F], reflecting the fact that cats provides a tailRecM.
  • MonadError
    • Similar requirements to Monad
  • Monoid
  • Order
  • Profunctor
  • Semigroup
  • Show
    • The cats → scalaz conversion requires a Show.ContravariantShow (which is the supertype of Show), just for extra flexibility. This should be invisible to users 99% of the time.
  • Strong
  • Traverse

Note that some typeclasses exist in one framework but not in the other (e.g. Group in cats, or Split in scalaz). In these cases, no conversion is attempted, though practical conversion may be achieved through more specific instances (e.g. Arrow is a subtype of Split, and Arrow will convert).

And don't get me started on the whole Bind vs BindRec mess. I make no excuses for that conversion. Just trying to make things work as reasonably as possible, given the constraints of the upstream frameworks.

Let me know if I missed anything! Comprehensive lists of typeclasses in either framework are hard to come by.


Datatype conversions are explicit, meaning that users must insert syntax which triggers the conversion. In other words, there is no implicit coercion between data types: a method call is required. For example, converting between scalaz.Free and is done via the following:

val f1: scalaz.Free[F, A] = ???
val f2:[F, A] = f1.asCats
val f3: scalaz.Free[F, A] = f2.asScalaz
Cats Direction Scalaz
cats.Eval 👈👉 scalaz.Free.Trampoline
cats.Eval 👈 scalaz.Name
cats.Eval 👈 scalaz.Need
cats.Eval 👈 scalaz.Value
cats.arrow.FunctionK 👈👉 scalaz.~> 👈👉 scalaz.Cokleisli 👈👉 scalaz.Const 👈👉 scalaz.Coproduct 👈👉 scalaz.EitherT 👈👉 scalaz.IndexedStateT 👈👉 scalaz.\&/ 👈👉 scalaz.Kleisli 👈👉 scalaz.NonEmptyList 👈👉 scalaz.OneAnd 👈👉 scalaz.OptionT 👈 scalaz.MaybeT 👈👉 scalaz.RWST 👈👉 scalaz.Validation 👈👉 scalaz.ValidationNel 👈👉 scalaz.WriterT 👈👉 scalaz.Free
scala.Option 👈 scalaz.Maybe
scala.util.Either 👈👉 scalaz.\/

Note that the asScalaz/asCats mechanism is open and extensible. To enable support for converting some type "cats type" A to an equivalent "scalaz type" B, define an implicit instance of type shims.conversions.AsScalaz[A, B]. Similarly, for some "scalaz type" A to an equivalent "cats type" B, define an implicit instance of type shims.conversions.AsCats[A, B]. Thus, a pair of types, A and B, for which a bijection exists would have a single implicit instance extending AsScalaz[A, B] with AsCats[B, A] (though the machinery does not require this is handled with a single instance; the ambiguity resolution here is pretty straightforward).

Wherever extra constraints are required (e.g. the various StateT conversions require a Monad[F]), the converters require the cats variant of the constraint. This should be invisible under normal circumstances since shims itself will materialize the other variant if one is available.


At present, the asScalaz/asCats mechanism does not recursively convert nested structures. This situation most commonly occurs with monad transformer stacks. For example:

val stuff: EitherT[OptionT[Foo, ?], Errs, Int] = ???


The type of the final line is[scalaz.OptionT[Foo, ?], Errs, Int], whereas you might expect that it would be[[Foo, ?], Errs, Int]. It is technically possible to apply conversions in depth, though it require some extra functor constraints in places. The primary reason why this isn't done (now) is compile time performance, which would be adversely affected by the non-trivial inductive solution space.

It shouldn't be too much of a hindrance in any case, since the typeclass instances for the nested type will be materialized for both scalaz and cats, and so it doesn't matter as much exactly which nominal structure is in use. It would really only matter if you had a function which explicitly expected one thing or another.

The only exception to this rule is ValidationNel in scalaz and ValidatedNel in cats. Converting this composite type is a very common use case, and thus an specialized converter is defined:

val v: ValidationNel[Errs, Int] = ???

v.asCats   // => v2: ValidatedNel[Errs, Int]

Note that the scalaz.NonEmptyList within the Validation was converted to a within the resulting Validated.

In other words, under normal circumstances you will need to manually map nested structures in order to deeply convert them, but ValidationNel/ValidatedNel will Just Work™ without any explicit induction.


None of this would have been possible without some really invaluable assistance:

  • Guillaume Martres (@smarter), who provided the key insight into the scalac bug which was preventing the implementation of Capture (and thus, bidirectional conversions)
  • Christopher Davenport (@ChristopherDavenport), who contributed the bulk of shims-effect in its original form on scalaz-task-effect