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

Type inference


I have already outlined type inference earlier in the chapter. It is a feature of F# (as well as many other languages: C#, to begin with) that stems from its property of being statically typed. By following the natural code flow direction from top to bottom and from left to right, the F# compiler is capable of deriving types of values present in the code, including function types. This ability, in turn, allows you to omit explicit type declarations from the F# code. In the end, the code can be written faster, is quite succinct, and if it compiles, is consistent type-wise.

Relying on type inference is not mandatory when writing the F# code. Adding an explicit declaration to the code may be especially meaningful in the following scenarios:

  • When the types cannot be inferred and the compiler prompts for the explicit declaration

  • If the code's author believes that providing explicit type declaration in some cases may simplify the code understanding and improve its readability

The most...