Bird
Raised Fist0
C Sharp (C#)programming~3 mins

Why Predicate delegate type in C Sharp (C#)? - Purpose & Use Cases

Choose your learning style10 modes available
The Big Idea

What if you could write one method that adapts to any condition you dream up, without rewriting code?

The Scenario

Imagine you have a list of numbers and you want to find all the even ones. You try to write separate code for each condition, like checking if a number is even, greater than 10, or less than 5, repeating similar loops and checks everywhere.

The Problem

This manual way means writing lots of repeated code, which is slow and easy to mess up. Every time you want a new condition, you write a new loop or method, making your code bulky and hard to change.

The Solution

The Predicate delegate type lets you write one flexible method that takes any condition you want as a parameter. You just pass in the rule (the predicate), and the method uses it to pick items. This keeps your code clean, reusable, and easy to update.

Before vs After
✗ Before
List<int> evens = new List<int>();
foreach(var n in numbers) {
  if(n % 2 == 0) evens.Add(n);
}
✓ After
List<int> evens = numbers.FindAll(n => n % 2 == 0);
What It Enables

You can create powerful, reusable methods that work with any condition, making your programs smarter and simpler.

Real Life Example

Filtering a list of customers to find those who are active and live in a certain city by just changing the predicate condition without rewriting the whole search logic.

Key Takeaways

Manual filtering repeats code and is hard to maintain.

Predicate delegate lets you pass conditions as parameters.

This makes your code flexible, reusable, and easier to read.

Practice

(1/5)
1.

What does a Predicate<T> delegate represent in C#?

easy
A. A method that takes a parameter of type T and returns a boolean indicating a condition.
B. A method that takes no parameters and returns void.
C. A method that takes two parameters and returns an integer.
D. A method that returns a string representation of an object.

Solution

  1. Step 1: Understand the Predicate delegate signature

    A Predicate delegate always takes one parameter of type T and returns a boolean value.
  2. Step 2: Match the description to the options

    A method that takes a parameter of type T and returns a boolean indicating a condition correctly describes this signature as a method taking T and returning bool.
  3. Final Answer:

    A method that takes a parameter of type T and returns a boolean indicating a condition. -> Option A
  4. Quick Check:

    Predicate<T> = method(T) returns bool [OK]
Hint: Predicate always returns true or false for a given input [OK]
Common Mistakes:
  • Confusing Predicate with Action or Func delegates
  • Thinking Predicate returns void or other types
  • Assuming Predicate takes multiple parameters
2.

Which of the following is the correct syntax to declare a Predicate delegate for integers?

?
easy
A. Predicate<int> isPositive = x => x > 0;
B. Predicate<int> isPositive = (int x) => { return x; };
C. Predicate<int> isPositive = x => x + 1;
D. Predicate<int> isPositive = () => true;

Solution

  1. Step 1: Check the lambda expression return type

    Predicate<int> expects a method returning bool. Predicate<int> isPositive = x => x > 0; returns x > 0, which is bool.
  2. Step 2: Verify parameter and return correctness

    Predicate<int> isPositive = (int x) => { return x; }; returns x (int), not bool. Predicate<int> isPositive = x => x + 1; returns x + 1 (int), not bool. Predicate<int> isPositive = () => true; has no parameter but Predicate requires one.
  3. Final Answer:

    Predicate<int> isPositive = x => x > 0; -> Option A
  4. Quick Check:

    Predicate<int> = int input => bool output [OK]
Hint: Predicate must return bool, not int or void [OK]
Common Mistakes:
  • Returning int instead of bool
  • Missing parameter in lambda
  • Using incorrect lambda syntax
3.

What will be the output of the following C# code?

using System;
class Program {
    static void Main() {
        Predicate<string> isLong = s => s.Length > 5;
        string[] words = {"apple", "banana", "pear"};
        int count = 0;
        foreach (var word in words) {
            if (isLong(word)) count++;
        }
        Console.WriteLine(count);
    }
}
medium
A. 3
B. 2
C. 1
D. 0

Solution

  1. Step 1: Understand the Predicate condition

    The predicate checks if the string length is greater than 5.
  2. Step 2: Count words with length > 5

    "apple" length 5 (false), "banana" length 6 (true), "pear" length 4 (false). Only "banana" passes.
  3. Final Answer:

    2 -> Option B
  4. Quick Check:

    Words with length > 5 are "banana" only, count = 1 [Incorrect]
Hint: Count items where predicate returns true [OK]
Common Mistakes:
  • Counting words with length equal to 5
  • Misreading predicate condition
  • Assuming all words pass the test
4.

Identify the error in this code using a Predicate delegate:

Predicate<int> isEven = n => n % 2 == 0;
int[] numbers = {1, 2, 3, 4};
int evenCount = 0;
foreach (int num in numbers) {
    if (isEven) evenCount++;
}
Console.WriteLine(evenCount);
medium
A. The Predicate delegate is not assigned correctly.
B. The foreach loop variable should be declared as var.
C. The if condition should call the delegate with an argument.
D. The Console.WriteLine statement is missing parentheses.

Solution

  1. Step 1: Check how Predicate is used in if condition

    The code uses if (isEven) which checks the delegate itself, not its result.
  2. Step 2: Correct usage requires calling the delegate with an argument

    It should be if (isEven(num)) to evaluate the condition for each number.
  3. Final Answer:

    The if condition should call the delegate with an argument. -> Option C
  4. Quick Check:

    Call Predicate with input: isEven(num) [OK]
Hint: Always call Predicate with an argument inside if [OK]
Common Mistakes:
  • Using delegate name without parentheses
  • Confusing delegate variable with method call
  • Ignoring parameter requirement
5.

You want to filter a list of integers to keep only positive even numbers using a Predicate delegate. Which of the following implementations correctly combines these conditions?

hard
A. Predicate<int> isPositiveEven = x => x % 2 == 0;
B. Predicate<int> isPositiveEven = x => x > 0 || x % 2 == 0;
C. Predicate<int> isPositiveEven = x => x < 0 && x % 2 == 0;
D. Predicate<int> isPositiveEven = x => x > 0 && x % 2 == 0;

Solution

  1. Step 1: Understand the filtering requirement

    We want numbers that are both positive and even.
  2. Step 2: Analyze each option's condition

    Predicate<int> isPositiveEven = x => x > 0 && x % 2 == 0; uses AND (&&) to require both conditions true. Predicate<int> isPositiveEven = x => x > 0 || x % 2 == 0; uses OR (||), allowing positives or evens, which is incorrect. Predicate<int> isPositiveEven = x => x < 0 && x % 2 == 0; checks for negative and even, wrong sign. Predicate<int> isPositiveEven = x => x % 2 == 0; checks only even, missing positivity.
  3. Final Answer:

    Predicate<int> isPositiveEven = x => x > 0 && x % 2 == 0; -> Option D
  4. Quick Check:

    Use AND to combine conditions for filtering [OK]
Hint: Use && to combine multiple conditions in Predicate [OK]
Common Mistakes:
  • Using || instead of && for combined conditions
  • Checking wrong sign for positivity
  • Ignoring one of the required conditions
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard