answerkeytesting/11.answer.scala, Gen.scala: SGen: map: commented-out line removedRob Dickens1 year ago
answers/src/main/scala/fpinscalatesting/11.answer.scala, Gen.scala: SGen: map: commented-out line removedRob Dickens1 year ago
exercises/src/main/scala/fpinscalaBrings consistency to the unimplemented functionsAdam Fisher3 months ago
projectUpdate buildAdam Fisher3 months ago
.gitignoreAdded information regarding encrypted file systems and information on how to create eclipse projects.Martin Thomalla2 years ago
.travis.ymlEnable container-based infrastructure for Travis CIMichael Ummels2 years ago
LICENSEadded part 1 exercises, answers, hintsPaul Chiusano4 years ago
README.mdUpdate README.mdRĂșnar1 year ago
build.sbtUpdate buildAdam Fisher3 months ago
sbtUpdate buildAdam Fisher3 months ago
sbt-launch.jarUpdate buildAdam Fisher3 months ago
sbt.batUpdate sbt.batPaul Chiusano2 years ago
sbt.cmdUpdate sbt.cmdPaul Chiusano2 years ago

Build status Join the chat at

This repository contains exercises, hints, and answers for the book Functional Programming in Scala. Along with the book itself, it's the closest you'll get to having your own private functional programming tutor without actually having one.

Here's how to use this repository:

Each chapter in the book develops a fully working library of functions and data types, built up through a series of exercises and example code given in the book text. The shell of this working library and exercise stubs live in exercises/src/main/scala/fpinscala/<chapter-description>, where <chapter-description> is a package name that corresponds to the chapter title (see below). When you begin working on a chapter, we recommend you open the exercise file(s) for that chapter, and when you encounter exercises, implement them in the exercises file and make sure they work.

If you get stuck on an exercise, let's say exercise 4 in the chapter, you can find hints in answerkey/<chapter-description>/04.hint.txt (if no hints are available for a problem, the file will just have a single '-' as its contents) and the answer along with an explanation of the answer and any variations in answerkey/<chapter-description>/04.answer.scala or 04.answer.markdown. The finished Scala modules, with all answers for each chapter live in answers/src/main/scala/fpinscala/<chapter-description>. Please feel free to submit pull requests for alternate answers, improved hints, and so on, so we can make this repo the very best resource for people working through the book.

Chapter descriptions:

  • Chapter 2: gettingstarted
  • Chapter 3: datastructures
  • Chapter 4: errorhandling
  • Chapter 5: laziness
  • Chapter 6: state
  • Chapter 7: parallelism
  • Chapter 8: testing
  • Chapter 9: parsing
  • Chapter 10: monoids
  • Chapter 11: monads
  • Chapter 12: applicative
  • Chapter 13: iomonad
  • Chapter 14: localeffects
  • Chapter 15: streamingio

To build the code for the first time, if on windows:

$ .\sbt.cmd

If on mac/linux, first make sure you have not checked out the code onto an encrypted file system, otherwise you will get compile errors regarding too long file names (one solution is to put the fpinscala repo on a unencrypted usb key, and symlink it into your preferred code location).

$ chmod a+x ./sbt
$ ./sbt

This will download and launch sbt, a build tool for Scala. Once it is finished downloading, you'll get a prompt from which you can issue commands to build and interact with your code. Try the following:

> project exercises
> compile

This switches to the exercises project, where your code lives, and compiles the code. You can also do:

> console

to get a Scala REPL with access to your exercises, and

> run

To get a menu of possible main methods to execute.

To create project files for the eclipse IDE you can install the sbteclipse sbt plugin. This makes a new command available in sbt:

> eclipse

All code in this repository is MIT-licensed. See the LICENSE file for details.

Have fun, and good luck! Also be sure to check out the community wiki for the chapter notes, links to more reading, and more.

Paul and RĂșnar

About FluentSend Feedback