Book Image

Learning Functional Programming in Go

By : Lex Sheehan
Book Image

Learning Functional Programming in Go

By: Lex Sheehan

Overview of this book

Lex Sheehan begins slowly, using easy-to-understand illustrations and working Go code to teach core functional programming (FP) principles such as referential transparency, laziness, recursion, currying, and chaining continuations. This book is a tutorial for programmers looking to learn FP and apply it to write better code. Lex guides readers from basic techniques to advanced topics in a logical, concise, and clear progression. The book is divided into four modules. The first module explains the functional style of programming: pure functional programming, manipulating collections, and using higher-order functions. In the second module, you will learn design patterns that you can use to build FP-style applications. In the next module, you will learn FP techniques that you can use to improve your API signatures, increase performance, and build better cloud-native applications. The last module covers Category Theory, Functors, Monoids, Monads, Type classes and Generics. By the end of the book, you will be adept at building applications the FP way.
Table of Contents (21 chapters)
Title Page
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Index

Understanding functors


A functor is a structure-preserving transformation between categories. In other words, a functor is a mappable type. Let's see what that means with an example.

An imperative versus pure FP example

Suppose we start with a slice of ints, ints := []int{1,2,3}.

In imperative programming, we write all the scaffold code to implement exactly how to process this slice of ints. In pure FP, however, we tell our functor what we want the loop to do:

Here's the output:

imperative loop: [2 3 4]
fp map: [2 3 4]

Let's see how this works.

What did that Map function do for us?  

The Map function abstracted the loop. We don't have to bother writing the same old range/for looping code. We simply pass in our original ints list and tell our functor to map that slice into a slice where each element is one greater than it was before. This is a lot like SQL, where we declare what data we want and let the database engine worry about how to get the data.

What possible benefits can this afford us?

Do we...