Custom event arguments in C Sharp (C#) - Time & Space Complexity

Time Complexity: Custom event arguments

O(n)

Understanding Time Complexity

When using custom event arguments in C#, it's important to understand how the program's work grows as events are raised and handled.

We want to know how the time to process events changes as more events or data are involved.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

public class MyEventArgs : EventArgs
{
    public int Value { get; set; }
}

public class Publisher
{
    public event EventHandler<MyEventArgs> OnChange;

    public void RaiseEvent(int n)
    {
        for (int i = 0; i < n; i++)
            OnChange?.Invoke(this, new MyEventArgs { Value = i });
    }
}

This code defines a custom event argument class and raises an event n times, passing data each time.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop that raises the event n times.
• How many times: Exactly n times, once per loop iteration.

How Execution Grows With Input

Each time we increase n, the number of event invocations grows directly with n.

Input Size (n)	Approx. Operations
10	10 event calls
100	100 event calls
1000	1000 event calls

Pattern observation: The work grows in a straight line as n increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to raise and handle events grows directly in proportion to the number of events raised.

Common Mistake

[X] Wrong: "Raising multiple events inside a loop is always constant time because each event is simple."

[OK] Correct: Each event call happens once per loop iteration, so total time grows with the number of events raised.

Interview Connect

Understanding how event handling scales helps you write responsive and efficient programs, a skill valued in many coding challenges and real projects.

Self-Check

"What if the event handler itself contains a loop that runs m times? How would the overall time complexity change?"