Book Image

Learning Functional Data Structures and Algorithms

By : Raju Kumar Mishra
Book Image

Learning Functional Data Structures and Algorithms

By: Raju Kumar Mishra

Overview of this book

Functional data structures have the power to improve the codebase of an application and improve efficiency. With the advent of functional programming and with powerful functional languages such as Scala, Clojure and Elixir becoming part of important enterprise applications, functional data structures have gained an important place in the developer toolkit. Immutability is a cornerstone of functional programming. Immutable and persistent data structures are thread safe by definition and hence very appealing for writing robust concurrent programs. How do we express traditional algorithms in functional setting? Won’t we end up copying too much? Do we trade performance for versioned data structures? This book attempts to answer these questions by looking at functional implementations of traditional algorithms. It begins with a refresher and consolidation of what functional programming is all about. Next, you’ll get to know about Lists, the work horse data type for most functional languages. We show what structural sharing means and how it helps to make immutable data structures efficient and practical. Scala is the primary implementation languages for most of the examples. At times, we also present Clojure snippets to illustrate the underlying fundamental theme. While writing code, we use ADTs (abstract data types). Stacks, Queues, Trees and Graphs are all familiar ADTs. You will see how these ADTs are implemented in a functional setting. We look at implementation techniques like amortization and lazy evaluation to ensure efficiency. By the end of the book, you will be able to write efficient functional data structures and algorithms for your applications.
Table of Contents (20 chapters)
Learning Functional Data Structures and Algorithms
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Node definitions


Similar to lists, our binary tree is a trait, BinTree[+A]:

sealed trait BinTree[+A] 
case object Leaf extends BinTree[Nothing] 
case class Branch[A](value: A, left: BinTree[A], right: BinTree[A]) extends BinTree[A] 

The sealed trait BinTree[+A] array defines a sealed trait. As it is sealed, we can extend it only in the same source file. We saw in Chapter 3, Lists how this helps the compiler to check for exhaustive pattern matching:

case object Leaf extends BinTree[Nothing] 

The Leaf node is a terminator node, just like we have the Nil node in lists. Just like Nil, Leaf is a case object, as we just need only one instance of it:

case class Branch[A](value: A, left: BinTree[A], right: BinTree[A]) extends BinTree[A] 

The Branch node holds a value, of type A, and a left and right subtree. These subtrees could be either branches or leaves.

Thus, we define the binary tree in terms of itself; in other words, it is a recursively defined structure, similar to List:

Note

Note that this...