Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
F# 4.0 Design Patterns

You're reading from   F# 4.0 Design Patterns Solve complex problems with functional thinking

Arrow left icon
Product type Paperback
Published in Nov 2016
Publisher Packt
ISBN-13 9781785884726
Length 318 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Gene Belitski Gene Belitski
Author Profile Icon Gene Belitski
Gene Belitski
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Begin Thinking Functionally FREE CHAPTER 2. Dissecting F# Origins and Design 3. Basic Functions 4. Basic Pattern Matching 5. Algebraic Data Types 6. Sequences - The Core of Data Processing Patterns 7. Advanced Techniques: Functions Revisited 8. Data Crunching – Data Transformation Patterns 9. More Data Crunching 10. Type Augmentation and Generic Computations 11. F# Expert Techniques 12. F# and OOP Principles/Design Patterns 13. Troubleshooting Functional Code

Wildcard matching


If I put the preceding scripts into Visual Studio, the F# source code editor will draw a blue warning squiggle line under the ``compare me`` comparison expression, indicating that the set of rules in this match construction is not exhaustive, as shown in the following screenshot:

An example of an incomplete pattern matching

The compiler even gives a sample value of ``compare me``, which is not going to match. Although this value is not present within the definition of type Multiples, if I synthetically create this value as enum<Multiples>(1) and feed it as an argument into transformB, the result would be the run-time exception of type Microsoft.FSharp.Core.MatchFailureException. This situation should raise the following question: how would it be possible to put a match all rule into the match, which means anything that was not specified in preceding rules?

For this purpose, F# offers the special wildcard pattern  _ that matches anything that was not matched in the preceding...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime