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

Higher-kinded types


Higher-kinded types have the ability to reason about generic types with their type parameters as variables. Functors, Monads, and Applicative Functors are higher-kinded types and are not supported natively in the Swift 3.0 type system!

For curious readers, it is recommended to read the Swift Evolution Proposal (https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151214/002736.html) and the Generic manifesto (https://github.com/apple/swift/blob/master/docs/GenericsManifesto.md#higher-kinded-types).

According to the Generic Manifesto, higher-kinded types allow us to express the relationship between two different specializations of the same nominal type within a protocol. For example, if we think of the Self type in a protocol as really being Self<T>, it allows us to talk about the relationship between Self<T> and Self<U> for some other type U. For instance, it could allow the map operation on a collection to return a collection of the same kind...