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

An explicit form of pattern matching with match construction


Explicit match construction in F# belongs to control flow elements, along with if-then-else, or while-do. Of other F# bits and pieces, a match is a relatively complicated combination of the following parts and governing rules:

match comparison-expression with 
  | pattern-expression1 -> result-expression1 
  ......................................... 
  | pattern-expressionN -> result-expressionN 

It works in this manner, that is, comparison-expression is juxtaposed with each pattern-expression beginning with pattern-expression1 and goes down the list until either the first match occurs, or passing pattern-expressionN still non-matched. If a match is found for pattern-expressionX, then the result of the entire construction is the result of result-expressionX. If no matches are found, then MatchFailureException is thrown, indicating that the match cases were incomplete.

The key points of pattern matching that are often missing...