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

Sequence and the code performance


Sequences are, without doubt, extremely powerful members of the functional programmer tool belt. However, they are not free of gotchas that may hurt the performance badly. It is best that they are known and avoided. A few of them are as follows:

  • Unfortunate materialization, which may be either unnecessary/premature elements materialization or the other way around, missing elements materialization.

  • Data laziness, in concert with the non-preserving once current element values, can severely hurt the performance in a situation where the algorithm requires multiple traversals or where calculating elements is expensive. The developer should be able to compensate for these detrimental factors by applying patterns such as caching and/or memoization.

  • Often, when composing data processing pipelines, the developer may carelessly use a library function that unexpectedly requires them to enumerate the entire sequence. This is not necessarily a bad thing, but it should be...