Explicit interface implementation in C Sharp (C#) - Time & Space Complexity

Time Complexity: Explicit interface implementation

O(1)

Understanding Time Complexity

Let's see how the time it takes to run code changes when using explicit interface implementation in C#.

We want to know how the program's steps grow as input size changes.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

interface IPrinter
{
    void Print();
}

class Document : IPrinter
{
    void IPrinter.Print() {
        for (int i = 0; i < 100; i++) {
            System.Console.WriteLine("Printing page " + i);
        }
    }
}
    

This code shows a class implementing an interface explicitly, printing 100 pages in a loop.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop inside the explicit interface method runs 100 times.
• How many times: Exactly 100 times each time the Print method is called.

How Execution Grows With Input

Here, the loop count is fixed at 100, so the number of steps does not change with input size.

Input Size (n)	Approx. Operations
10	100 (fixed)
100	100 (fixed)
1000	100 (fixed)

Pattern observation: The work stays the same no matter how big the input is.

Final Time Complexity

Time Complexity: O(1)

This means the time to run the method stays constant, no matter the input size.

Common Mistake

[X] Wrong: "Explicit interface implementation makes the method slower because it adds overhead."

[OK] Correct: The way the method is implemented does not change how many times the loop runs or how long it takes; it only changes how you call the method.

Interview Connect

Understanding how explicit interface implementation affects performance helps you explain your code choices clearly and shows you know how code structure relates to efficiency.

Self-Check

"What if the loop count was based on a variable input size instead of a fixed 100? How would the time complexity change?"