Intersection types in practice in PHP - Time & Space Complexity

Time Complexity: Intersection types in practice

O(1)

Understanding Time Complexity

Let's see how using intersection types affects the time it takes for PHP code to run.

We want to know how the program's work grows when input changes.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

interface Logger {
    public function log(string $msg): void;
}

interface FileWriter {
    public function write(string $data): void;
}

function saveAndLog(FileWriter&Logger $obj, string $data): void {
    $obj->write($data);
    $obj->log("Data saved");
}

// Assume $obj implements both interfaces
saveAndLog($obj, "Hello World");
    

This code uses an intersection type to require an object that can both write files and log messages.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Two method calls on the same object.
• How many times: Exactly twice per function call.

How Execution Grows With Input

Each time we call the function, it does two actions regardless of input size.

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

Pattern observation: Operations remain constant regardless of input size.

Final Time Complexity

Time Complexity: O(1)

This means the time remains constant regardless of input size.

Common Mistake

[X] Wrong: "Using intersection types makes the code slower because it checks multiple interfaces at once."

[OK] Correct: Intersection types are a compile-time check and do not add extra work when the program runs.

Interview Connect

Understanding how type checks affect performance helps you write clear and efficient code, a skill valued in many coding challenges.

Self-Check

"What if the function called a method inside a loop over a large array? How would the time complexity change?"