Fortsätt till huvudinnehåll

C# Delegates, Action, Func, or Predicate

Introduction

As a previous C developer I am used to working with function pointers and I found the C# Delegates quite easy to work with in comparison. One thing that made me a bit confused initially however were the Delegate types defined in the .NET framework. Why would I want to bother with Actions, Funcs, and Predicates? After reading up on them I almost never define custom Delegates anymore. I will try to explain their use cases below.

Delegates

A Delegate in C# is similar to a function pointer in C or C++. You can always define a custom Delegate that matches any method signature you want. However, the .NET Framework defines a number of Delegates you can use so that you don't have to define your own. These Delegates are grouped into three different Delegate groups, Actions, Funcs, and Predicates.

Actions

An Action is, as the name implies, a Delegate that encapsulates a method that performs an operation and where you expect no result to be returned. The Action Delegate takes zero or more input parameters (up to 16). Typical actions are methods like Print(msg), Show(window), or Beep().

Funcs

A Func is a Delegate that encapsulates a method that performs an operation and returns a result. Similar to the Action Delegate it takes zero or more input parameters. The difference is that it must return a value or reference. Typical functions are methods like Add(i, j), Max(values[]), or Join(separator, strings[]).

Predicates

Finally, a Predicate is a Delegate that encapsulates a method that takes a single input parameter and returns a boolean. It is a special kind of Func used to answer questions such as CanExecute(conditional), IsWithinRange(value), or OlderThan(years).

There are a lot of methods in the .NET Framework that takes Delegates as input parameters. If you call a method with a Lambda Expression as an input parameter you are defining a Delegate that the called method will invoke. LINQ, as an example, relies heavily on Delegates.

If you don't have a lot of experience with Delegates I recommend reading up on them (links are provided below) and start using them where appropriate.

Learn more

The Delegate Class
Action Delegate
Func Delegate
Predicate Delegate
Lambda Expressions

Kommentarer

Skicka en kommentar

Populära inlägg i den här bloggen

Does TDD really improve software quality?

I have asked myself this question several times, and searched for answers, without coming up with any clear answer. Therefore I have decided to go hard core TDD for a longer period of time (at least 6 months) to really evaluate the effects. There are several things that I find confusing when it comes to TDD. One example is what actually defines a unit test. What is a "unit" anyway? After reading a bit about it I found a text claiming that the "unit" is "a unit of work", i.e. something quite small. Like converting a string to UPPERCASE or splitting a string into an ['a','r', 'r', 'a', 'y'] of chars. This work is usually performed by a single call to a single method in a single, isolated, class. So, what does it mean that a class is isolated? Does it mean that it doesn't have any dependencies to other classes? NO! In the context of TDD it means that any dependencies are supplied by the test environment, for exa...
3 kommentarer
Läs mer

Codility tasks - Part I

I was recently faced with two codility tasks when applying for a job as an Embedded Software Engineer. For those of you who arn't familiar with Codility you can check out their website here:  www.codility.com Task one - Dominator The first task was called Dominator. The goal was to, given a std::vector of integers, find an integer that occurs in more than half of the positions in the vector. If no dominator was found -1 should be returned. My approach was to loop through the vector from the first to the last element, using a std::map to count the number of occurences of each integer. If the count ever reached above half the size of the vector I stopped and returned that integer and if I reached the end without finding a dominator I returned -1. So was that a good approach? Well, the reviewer at the company rated the solution as 'pretty ok'. His preferred solution was store the first integer in the array and set a counter to 1. Then loop through the remaining i...
7 kommentarer
Läs mer

Codility tasks - Part II

Now, the second codility task I was faced with was a bit tougher. The goal was to create a function that, given a vector of integers A and an integer K, returned the number of integer pairs in the vector that, when added, sums up to K. Let me give you an example. Assume that you are given a vector A = [0, -1, 3, 2, -5, 7] and K = 2. Possible combinations to get K are (0, 2), (-1, 3), (3, -1), (2, 0),  (-5, 7), and (7, -5). In other words, the function should return 6. Now, how did I solve this task? The first solution that came to mind involved nested for-loops. The outer loop picking one integer at the time from the vector and the inner loop adding the integer to the others one by one to see if the result is K. This solution works, but it does not scale well. Time complexity will be O(N**2) ,   something that for large vectors will result in very long execution times. My second approach was to use my old friend, the integer counter, and count all occurences of each...
2 kommentarer
Läs mer