aboutsummaryrefslogtreecommitdiff

Real World Haskell solutions

These are solutions to exercises from me reading the first edition of the the Real World Haskell book. Publishing the solutions like this helps me in being more thorough in reading the book. I also hope they will be helpful in your journey to the world of Haskell.

The goal is to provide solutions to all the exercises. I'm adding them gradually as I'm progressing through the book.

There is often more than one solution to an exercise. If your solution is different but meets the assignment, it is the right one.

My original intention was for the exercises to be solved as by a beginner, with all the things that a seasoned Haskell programmer would have done differently. The solutions should have mostly used only knowledge from the preceding parts of the book. Exceptions to this were cases where such approach would lead to too many additional lines of code or to distracting the reader from the main idea of an exercise. Advanced topics from the subsequent chapters should have been avoided, though.

However, in about two thirds of the book I finally had to admit to myself that it was too challenging and got stuck. Then I took a detour to other Haskell books that were more suitable for beginners. Now I returned and I'm going to see how much difference it has made and whether I will be able to continue in the exercises.

Running the code on new systems

The book was published in 2008. Even though it's old, most of the code can still be compiled with recent versions of GHC without any change. Only a few parts required minor modifications or additions. These are described in the comments in the source files of the exercise solutions.

Where more work was needed, I wanted to keep the code in its original form as much as possible instead of rewriting it for new GHC or libraries. These cases are described here.

Chapter 23: GUI programming with gtk2hs

This chapter uses more libraries than the other chapters and I was not able to install all of them using recent stack resolvers (sets of GHC and specific package versions) and Cabal versions.

I decided to create a reproducible environment consisting of an older GHC and compatible versions of the required libraries. Eventually, I was able to compile and run the application.

See the README in the ch23/support directory.

Exercises

There are a few kinds of exercises:

  • Describe what happens when you run the code
  • Answer a question
  • Write an implementation

Solutions to the first two kinds of exercises are provided in comments in Haskell source files.

Ambiguity and mistakes in the assignments

Assignments of the exercises are taken exactly as they are in the printed version of the book without correcting any mistakes. Those are corrected in comments immediately following the assignments.

Some exercises are unclear or they seem to contain contradicting information. In these cases I describe my additional assumptions and thought process in comments.

Solutions using code from the examples

Some solution implementations use the example code from the book. The complete examples repository these solutions are base on is added as a submodule in the 'examples' directory.

If a solution of an exercise depends on more source code from the examples, the whole files are copied to a directory of that solution.

If not much code is needed, then just the required parts are copied directly to the file with implementation and marked by comments.

Platform

The solutions are implemented and tested in a Linux environment. This also includes solutions that could have been made multiplatform.

List of the exercises

Format of an exercise label is '{Module_}\<chapter>_\<group>_\<exercise>'. Some chapters contain more groups of exercises. To differentiate those, an exercise group letter is included (the exact letters don't have a connection to the book). To make the exercise groups more visible in the list the first exercise of a group is in bold italics.

If a solution is intended to be used in solutions to other exercises, to reduce code duplication, it is imported as a Haskell module. For this to work, the naming conventions for Haskell modules need to be followed. The names of such source files are prefixed with 'Module_'.

Exercise Solved Page Chapter
1_a_1 yes 16 1. Getting started
1_a_2 yes
1_a_3 yes
1_a_4 yes
2_a_1 yes 25 2. Types and functions
2_b_1 yes 39
2_b_2 yes
2_b_3 yes
3_a_1 yes 60 3. Defining types, streamlining functions
3_a_2 yes
3_b_1 yes 69
3_b_2 yes, in 3_b_1
3_b_3 yes
3_b_4 yes
3_b_5 yes
3_b_6 yes 70
3_b_7 yes
3_b_8 yes
3_b_9 yes
3_b_10 yes, in 3_b_9
3_b_11 yes, in 3_b_9
3_b_12 yes, in 3_b_9
4_a_1 yes 84 4. Functional programming
4_a_2 yes
4_a_3 yes
4_a_4 yes
4_b_1 yes, in 4_b_2 97
4_b_2 yes 98
4_b_3 yes
4_b_4 yes
4_b_5 yes, in 4_b_6
4_b_6 yes
4_b_7 yes
4_b_8 yes, in 4_b_9
4_b_9 yes
4_b_10 yes
5_a_1 yes 130 5. Writing a library: working with JSON data
5_a_2 yes, in 5_a_1
6_a_1 yes 162 6. Using typeclasses
6_a_2 yes
8_a_1 yes 205 8. Efficient file processing, regular expressions, and file name matching
8_a_2 yes
8_b_1 yes, in 8_a_2 210
8_b_2 yes
8_b_3 yes
Module_8_c_1 yes 211
8_c_2 yes
8_d_1 yes 212
9_a_1 yes 221 9. I/O case study: a library for searching the filesystem
9_b_1 yes 228
9_b_2 yes
Module_9_b_3 yes
9_b_4 yes
9_c_1 yes 232
9_c_2 yes
9_c_3 yes
9_d_1 yes 234
9_d_2 yes
10_a_1 yes 254 10. Code case study: parsing a binary data format
10_a_2 yes, in 10_a_1
10_a_3 yes, in 10_a_1
12_a_1 yes 274 12. Barcode recognition
12_a_2 yes, in 12_a_1
12_a_3 yes, in 12_a_1
13_a_1 yes 316 13. Data structures
14_a_1 yes 352 14. Monads
15_a_1 yes 382 15. Programming with monads
15_a_2 yes, in 15_a_1
15_a_3 yes
16_a_1 yes 403 16. Using parsec
16_a_2 yes
16_a_3 yes
16_a_4 yes
18_a_1 yes 436 18. Monad transformers
18_a_2 yes
18_a_3 yes, in 18_a_2
18_b_1 yes 441
19_a_1 yes 462 19. Error handling
Module_19_b_1 yes 465
19_b_2 yes
19_b_3 yes, in 19_b_2
23_a_1 yes 529 23. GUI programming with gtk2hs
23_a_2 yes, in 23_a_1
23_a_3 yes
24_a_1 yes 542 24. Concurrent and multicore programming
24_a_2 yes
24_b_1 yes 551
24_b_2 yes, in 24_b_1
26_a_1 yes 610 26. Advanced library design: building a Bloom filter
26_a_2 yes

Bug reports

If you find an error in a solution or anything that should be described more clearly, feel free to let me know by opening an issue here or a pull request here.