Book Image

Hands-On Functional Programming with C++

By : Alexandru Bolboaca
Book Image

Hands-On Functional Programming with C++

By: Alexandru Bolboaca

Overview of this book

Functional programming enables you to divide your software into smaller, reusable components that are easy to write, debug, and maintain. Combined with the power of C++, you can develop scalable and functional applications for modern software requirements. This book will help you discover the functional features in C++ 17 and C++ 20 to build enterprise-level applications. Starting with the fundamental building blocks of functional programming and how to use them in C++, you’ll explore functions, currying, and lambdas. As you advance, you’ll learn how to improve cohesion and delve into test-driven development, which will enable you in designing better software. In addition to this, the book covers architectural patterns such as event sourcing to help you get to grips with the importance of immutability for data storage. You’ll even understand how to “think in functions” and implement design patterns in a functional way. By the end of this book, you’ll be able to write faster and cleaner production code in C++ with the help of functional programming.
Table of Contents (23 chapters)
Free Chapter
1
Section 1: Functional Building Blocks in C++
7
Section 2: Design with Functions
12
Section 3: Reaping the Benefits of Functional Programming
17
Section 4: The Present and Future of Functional Programming in C++

Summary

Property-based tests are a welcome addition to the example-based tests we've known and used for many years. They show us how we can combine data generation with a bit of analysis to both remove duplication from tests and find cases we hadn't considered.

Property-based tests are enabled by data generators that are very easy to implement using pure functions. Things will become even easier with lazy evaluation coming in C++ 20 or with the ranges library.

But the core technique in property-based testing is to identify the properties. We've seen two ways to do that—the first by analyzing the examples, and the second by writing the example-based tests, removing duplication to turn them into data-driven tests, and then replacing the rows of data with properties.

Finally, remember that property-based tests are code, and they need to be very clean, easy to...