Cats is a library which provides abstractions for functional programming in the Scala programming language. The name is a playful shortening of the word category.
Scala supports both object-oriented and functional programming, and this is reflected in the hybrid approach of the standard library. Cats strives to provide functional programming abstractions that are core, binary compatible, modular, approachable and efficient. A broader goal of Cats is to provide a foundation for an ecosystem of pure, typeful libraries to support functional programming in Scala applications.
For more detail about Cats’ motivations, go here.
Cats is currently available for Scala 2.10, 2.11 and 2.12, and Scala.js.
To get started with SBT, simply add the following to your
libraryDependencies += "org.typelevel" %% "cats-core" % "1.0.0-MF"
This will pull in the cats-core module. If you require some other
functionality, you can pick-and-choose from amongst these modules
(used in place of
cats-macros: Macros used by Cats syntax (required).
cats-kernel: Small set of basic type classes (required).
cats-core: Most core type classes and functionality (required).
cats-laws: Laws for testing type class instances.
cats-free: Free structures such as the free monad, and supporting type classes.
cats-testkit: lib for writing tests for type class instances using laws.
There are several other cats modules that are in separate repos so that they can maintain independent release cycles.
IOtype together with
cats-mtl: transformer typeclasses for cats’ Monads, Applicatives and Functors.
alleycats: cats instances and classes which are not lawful.
mouse: a small companion to cats that provides convenient syntax (aka extension methods)
Enhancing type inference
To use cats you’ll need sometimes support for improved type inference. To enable it for any supported Scalac version, use this sbt plugin.
Release notes for Cats are available in CHANGES.md.
Cats is still under active development. While we don’t anticipate any major redesigns, changes that are neither source nor binary compatible are to be expected in upcoming RC1 and 1.0 releases.
By sharing the same set of type classes, instances and data types provided by cats, projects can speak the same “cats language”, and integrate with each other with ease.
General purpose libraries to support pure functional programming
- Dogs: pure functional collections and data structures
- eff: functional effects and effect handlers (alternative to monad transformers)
- Freestyle: pure functional framework for Free and Tagless Final apps & libs
- iota: Fast [co]product types with a clean syntax
- Kittens: automatic type class derivation for Cats and generic utility functions
- mainecoon: Transform and compose tagless final encoded algebras
- Monocle: an optics library for Scala (and Scala.js) strongly inspired by Haskell Lens.
- newts: Defines newtypes compatible with cats type classes
- origami: monadic folds
- refined: simple refinement types for Scala
Libraries with more specific uses
- atto: friendly little text parsers
- circe: pure functional JSON library
- decline: A composable command-line parser
- doobie: a pure functional JDBC layer for Scala
- Fetch: efficient data access to heterogeneous data sources
- finch: Scala combinator library for building Finagle HTTP services
- Frameless: Expressive types for Spark
- FS2: compositional, streaming I/O library
- grafter: dependency-injection library using the
- hammock: Purely functional HTTP client
- http4s: A minimal, idiomatic Scala interface for HTTP
- monadic-html: Tiny DOM binding library for Scala.js
- Monix: high-performance library for composing asynchronous and event-based programs
- pureconfig: A boilerplate-free library for loading configuration files
- scanamo: simpler DynamoDB access for Scala
- seals: tools for schema evolution and language-integrated schemata
Feel free to submit a PR if you want a project you maintain to be added to this list.
The full-size cats logo is available for use for Cats related projects, contents, souvenirs, etc.
How can I contribute to Cats?
We welcome contributions to Cats and would love for you to help build Cats. See our contributor guide for more information about how you can get involved.
Discussion around Cats is currently happening on Github issue and PR pages as well as in two Gitter channels:
Gitter channel cats is for general user questions and discussions, and
Gitter channel cats-dev is dedicated for cats development related discussions. For people who wants to follow closely and/or to participate in the decisions in cats development, this is the room to join.
You can get an overview of who is working on what via Waffle.io.
People are expected to follow the Typelevel Code of Conduct when discussing Cats on the Github page, Gitter channel, or other venues.
We hope that our community will be respectful, helpful, and kind. If you find yourself embroiled in a situation that becomes heated, or that fails to live up to our expectations, you should disengage and contact one of the project maintainers in private. We hope to avoid letting minor aggressions and misunderstandings escalate into larger problems.
If you are being harassed, please contact one of us immediately so that we can support you.
Binary compatibility and versioning
1.0.0 release, we decided
to use MAJOR.MINOR.PATCH Semantic Versioning 2.0.0
going forward, which is different from the EPOCH.MAJOR.MINOR scheme common among
Java and Scala libraries (including the Scala lang).
Cats strives to provide a solid and stable foundation for an ecosystem of
FP libraries. Thus, we treat backward binary compatibility maintainence with a high priority.
In semantic versioning, backward breaking change is ONLY allowed between MAJOR versions.
We will maintain backward binary compatibility between PATCH AND MINOR versions.
For example, when we release cats
1.1.0, it will be backward binary compatible
with the previous
1.0.x versions. I.E. the new JAR will be a drop-in replacement for
the old one. This is critical when your application has a diamond
dependency on Cats - depending on two or more libraries that all depend on Cats.
If one library upgrades to the new
1.1.0 Cats before the other one does, your
application still runs thanks to this backward binary compatibility.
Also worth noting is that according to semantic versioning, MINOR version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated.
Any binary breaking changes will require a MAJOR version bump, which we will be very
cautious about. We will also consider using
organization and package name for major
versioning in the future. But that decision is yet to be made.
The current maintainers (people who can merge pull requests) are:
- ceedubs Cody Allen
- rossabaker Ross Baker
- johnynek P. Oscar Boykin
- travisbrown Travis Brown
- adelbertc Adelbert Chang
- peterneyens Peter Neyens
- edmundnoble Edmund Noble
- tpolecat Rob Norris
- stew Mike O’Connor
- non Erik Osheim
- mpilquist Michael Pilquist
- milessabin Miles Sabin
- djspiewak Daniel Spiewak
- fthomas Frank Thomas
- julien-truffaut Julien Truffaut
- kailuowang Kailuo Wang
We are currently following a practice of requiring at least two sign-offs to merge PRs (and for large or contentious issues we may wait for more). For typos or other small fixes to documentation we relax this to a single sign-off.
Copyright and License
All code is available to you under the MIT license, available at http://opensource.org/licenses/mit-license.php and also in the COPYING file. The design is informed by many other projects, in particular Scalaz.
Copyright the maintainers, 2015-2017.