Book Image

Swift Functional Programming - Second Edition

By : Dr. Fatih Nayebi
Book Image

Swift Functional Programming - Second Edition

By: Dr. Fatih Nayebi

Overview of this book

Swift is a multi-paradigm programming language enabling you to tackle different problems in various ways. Understanding each paradigm and knowing when and how to utilize and combine them can lead to a better code base. Functional programming (FP) is an important paradigm that empowers us with declarative development and makes applications more suitable for testing, as well as performant and elegant. This book aims to simplify the FP paradigms, making them easily understandable and usable, by showing you how to solve many of your day-to-day development problems using Swift FP. It starts with the basics of FP, and you will go through all the core concepts of Swift and the building blocks of FP. You will also go through important aspects, such as function composition and currying, custom operator definition, monads, functors, applicative functors,memoization, lenses, algebraic data types, type erasure, functional data structures, functional reactive programming (FRP), and protocol-oriented programming(POP). You will then learn to combine those techniques to develop a fully functional iOS application from scratch
Table of Contents (19 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface

Summary


In this chapter, we developed a backend with the Swift Vapor library, which handles the Todo items POST, GET, and DELETE. Then, we developed a frontend iOS application that leverages functional programming, reactive programming, and State management techniques declaratively. We started by developing our Todo model in a functional style, and then we developed a Store object and its extensions to handle State storage, and Action to handle State changes. We defined and used Lens to modify our properties and a WebServiceManager with reflection techniques to request for backend resources.

In this case study, we were able to use value types such as struct and enum and avoid classes. In fact, the only four classes in this case study are related to the iOS SDK (UIViewController, UITableViewController, UITableViewCell, and UIView subclasses). We were able to centralize all State mutations into the Store object, only using Action to change the State in the Store object. Although we did not...