Book Image

F# 4.0 Design Patterns

By : Gene Belitski
Book Image

F# 4.0 Design Patterns

By: Gene Belitski

Overview of this book

Following design patterns is a well-known approach to writing better programs that captures and reuses high-level abstractions that are common in many applications. This book will encourage you to develop an idiomatic F# coding skillset by fully embracing the functional-first F# paradigm. It will also help you harness this powerful instrument to write succinct, bug-free, and cross-platform code. F# 4.0 Design Patterns will start off by helping you develop a functional way of thinking. We will show you how beneficial the functional-first paradigm is and how to use it to get the optimum results. The book will help you acquire the practical knowledge of the main functional design patterns, the relationship of which with the traditional Gang of Four set is not straightforward. We will take you through pattern matching, immutable data types, and sequences in F#. We will also uncover advanced functional patterns, look at polymorphic functions, typical data crunching techniques, adjusting code through augmentation, and generalization. Lastly, we will take a look at the advanced techniques to equip you with everything you need to write flawless code.
Table of Contents (20 chapters)
F# 4.0 Design Patterns
Credits
About the Author
Acknowledgements
About the Reviewer
www.PacktPub.com
Preface

Morphing SOLID principles


Let's consider how the functional programming paradigm morphs the five basic principles of the object-oriented design known under this bold acronym of SOLID.

Single Responsibility Principle

The gist of Single Responsibility Principle (https://en.wikipedia.org/wiki/Single_responsibility_principle) (SRP), standing for the letter "S" in SOLID, in OOP terms is:

"There should never be more than one reason for a class to change"

In other words, if a class implementation is to be changed in response to two or more independent modifications to a functionality, this is an evidence of the Single Responsibility Principle (SRP) violation in its design. Following this principle in the OOP world entails designs consisting of many lean classes in lieu of fewer but bulkier classes.

If we consider a function as a degenerate case of class free of encapsulated data and having only the single method, then this is nothing but a quintessence of SRP applied. The following figure illustrates...