Book Image

C++ Reactive Programming

By : Praseed Pai, Peter Abraham
Book Image

C++ Reactive Programming

By: Praseed Pai, Peter Abraham

Overview of this book

Reactive programming is an effective way to build highly responsive applications with an easy-to-maintain code base. This book covers the essential functional reactive concepts that will help you build highly concurrent, event-driven, and asynchronous applications in a simpler and less error-prone way. C++ Reactive Programming begins with a discussion on how event processing was undertaken by different programming systems earlier. After a brisk introduction to modern C++ (C++17), you’ll be taken through language-level concurrency and the lock-free programming model to set the stage for our foray into the Functional Programming model. Following this, you’ll be introduced to RxCpp and its programming model. You’ll be able to gain deep insights into the RxCpp library, which facilitates reactive programming. You’ll learn how to deal with reactive programming using Qt/C++ (for the desktop) and C++ microservices for the Web. By the end of the book, you will be well versed with advanced reactive programming concepts in modern C++ (C++17).
Table of Contents (20 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Atomic types


All atomic types defined by the standard library can be found in the <atomic> header library. The system guarantees the atomicity to these types and all the related operations with these types. Some operations may not be atomic, but the system creates the illusion of atomicity in such cases. The standard atomic types use a member function, is_lock_free(), that allows the user to determine whether operations on a given type are done directly with atomic instructions (is_lock_free() returns true) or done using internal locks by the compiler and library (is_lock_free() returns false).

std::atomic_flag is different among all atomic types. The operations on this type are required to be atomic as per the standard. Hence, this doesn't provide the is_lock_free() member function. This is a very simple type with a minimal set of allowed operations such as test_and_set() (they can be either queried or set) or clear() (clears the value).

The remaining atomic types follow a similar signature...