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

.NET-imposed language features


Along with the features inherited from the language predecessors, the multitude of F# features was brought into the language for the sake of interoperability with the .NET platform.

F# adheres to .NET Common Language Infrastructure

Run-time arrangement for the F# code has been defined by .NET Common  Language  Infrastructure (CLI) and does not anyhow differ from the same of C# or VB.NET. F# compiler ingests F# source code file(s) and produces the intermediate code in assembly language named MSIL packaged as binary .NET assembly(ies). During code execution stage MSIL is converted into machine code as needed, or Just-in-time (JIT). Interoperability with other .NET languages is achieved as F#-produced assemblies do not anyhow differ from assemblies produced by C# or VB.NET. Similarly, the JIT compiler takes care of the target hardware platform providing portability. CLI also takes the burden of memory management on itself, making F# programs subject to .NET garbage...