Is there any benefit to this switch / pattern matching idea?

by

After trying to do such “functional” things in C# (and even attempting a book on it), I’ve come to the conclusion that no, with a few exceptions, such things don’t help too much.

The main reason is that languages such as F# get a lot of their power from truly supporting these features. Not “you can do it”, but “it’s simple, it’s clear, it’s expected”.

For instance, in pattern matching, you get the compiler telling you if there’s an incomplete match or when another match will never be hit. This is less useful with open ended types, but when matching a discriminated union or tuples, it’s very nifty. In F#, you expect people to pattern match, and it instantly makes sense.

The “problem” is that once you start using some functional concepts, it’s natural to want to continue. However, leveraging tuples, functions, partial method application and currying, pattern matching, nested functions, generics, monad support, etc. in C# gets very ugly, very quickly. It’s fun, and some very smart people have done some very cool things in C#, but actually using it feels heavy.

What I have ended up using often (across-projects) in C#:

  • Sequence functions, via extension methods for IEnumerable. Things like ForEach or Process (“Apply”? — do an action on a sequence item as it’s enumerated) fit in because C# syntax supports it well.
  • Abstracting common statement patterns. Complicated try/catch/finally blocks or other involved (often heavily generic) code blocks. Extending LINQ-to-SQL fits in here too.
  • Tuples, to some extent.

** But do note: The lack of automatic generalization and type inference really hinder the use of even these features. **

All this said, as someone else mentioned, on a small team, for a specific purpose, yes, perhaps they can help if you’re stuck with C#. But in my experience, they usually felt like more hassle than they were worth – YMMV.

Some other links:

More Related Contents:

  1. C# Switch Randomized [closed]
  2. Is there a better alternative than this to ‘switch on type’?
  3. Is “else if” faster than “switch() case”? [duplicate]
  4. C# switch statement limitations – why?
  5. Is there any significant difference between using if/else and switch-case in C#?
  6. Switch statement fallthrough in C#?
  7. Multiple cases in switch statement
  8. If vs. Switch Speed
  9. C# switch on type [duplicate]
  10. Why switch for enum accepts implicit conversion to 0 but no for any other integer?
  11. Switch case: can I use a range instead of a one number [duplicate]
  12. Variable declaration in a C# switch statement [duplicate]
  13. Using Case/Switch and GetType to determine the object [duplicate]
  14. How to make C# Switch Statement use IgnoreCase
  15. Switch case in C# – a constant value is expected
  16. Control cannot fall through from one case label
  17. Case Statement Block Level Declaration Space in C#
  18. Are .Net switch statements hashed or indexed?
  19. C# – Which is the best alternative to ‘switch on type’? [duplicate]
  20. How to switch between “possible” type of an object? [duplicate]
  21. Switch case on type c# [duplicate]
  22. In a switch vs dictionary for a value of Func, which is faster and why?
  23. Why is this switch on type case considered confusing?
  24. How to get Windows Explorer type look and feel inside my Application? [closed]
  25. How to call a VBScript file in a C# application?
  26. how to convert NameValueCollection to JSON string?
  27. Generic methods and method overloading
  28. Initialize library on Assembly load
  29. Regular expression to find and remove duplicate words
  30. Which objects can I use in a finalizer method?

Leave a Comment