Book Image

Mastering Functional Programming

Book Image

Mastering Functional Programming

Overview of this book

Functional programming is a paradigm specifically designed to deal with the complexity of software development in large projects. It helps developers to keep track of the interdependencies in the code base and changes in its state in runtime. Mastering Functional Programming provides detailed coverage of how to apply the right abstractions to reduce code complexity, so that it is easy to read and understand. Complete with explanations of essential concepts, practical examples, and self-assessment questions, the book begins by covering the basics such as what lambdas are and how to write declarative code with the help of functions. It then moves on to concepts such as pure functions and type classes, the problems they aim to solve, and how to use them in real-world scenarios. You’ll also explore some of the more advanced patterns in the world of functional programming such as monad transformers and Tagless Final. In the concluding chapters, you’ll be introduced to the actor model, which you can implement in modern functional languages, and delve into parallel programming. By the end of the book, you will be able to apply the concepts of functional programming and object-oriented programming (OOP)in order to build robust applications.
Table of Contents (17 chapters)

Chapter 11

  1. Whenever a thread needs to access a non-thread-safe resource, it takes a monitor on this resource. Monitor guarantees that only the thread that owns this monitor can work with his resource.
  2. A Deadlock is a situation when two threads depend on the progress of one another, and neither of them can't progress until the other thread does. So both threads stagnate. See chapter 11 for an example of how a deadlock can occur.
  3. An actor is a concurrency primitive. It has a mailbox where it can accept messages from other actors. It can send messages to other actors. It is defined in terms of reactions to the messages of other actors. Only one message can be processed at a time by a given actor. It is guaranteed that if an actor owns a non-thread-safe resource, no other actor is allowed to own it.

  1. Since only one actor controls a non-thread safe resource, there is no danger...