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?"

Practice

1. What does an intersection type like A&B mean in PHP?

easy

A. The value must be type B only.

B. The value can be either type A or type B.

C. The value must satisfy both type A and type B simultaneously.

D. The value must be type A only.

Solution

1. Step 1: Understand intersection type concept

   Intersection types require a value to meet all listed types at once, not just one.

2. Step 2: Apply to A&B

   The value must be both type A and type B simultaneously.

3. Final Answer:

   The value must satisfy both type A and type B simultaneously. -> Option C

4. Quick Check:

   Intersection means AND, so both types required [OK]

Hint: Intersection means all types must be met together [OK]

Common Mistakes:

• Confusing intersection (&) with union (|)
• Thinking it means either type A or B
• Assuming it means only one type

2. Which of the following is the correct syntax for declaring a function parameter with an intersection type of interfaces Countable and Iterator?

easy

A. function process(Countable&Iterator $obj) {}

B. function process(Countable|Iterator $obj) {}

C. function process(Countable, Iterator $obj) {}

D. function process(Countable & Iterator $obj) {}

Solution

1. Step 1: Recall intersection type syntax in PHP

   PHP uses the ampersand (&) without spaces and escaped as & in HTML to declare intersection types.

2. Step 2: Check each option

   function process(Countable&Iterator $obj) {} uses Countable&Iterator which is correct syntax for intersection types in PHP.

3. Final Answer:

   function process(Countable&Iterator $obj) {} -> Option A

4. Quick Check:

   Intersection uses & without spaces [OK]

Hint: Use & with no spaces for intersection types [OK]

Common Mistakes:

• Using | instead of & for intersection
• Adding spaces around &
• Using comma instead of &

3. Given the following code, what will be the output?

interface A { public function foo(): string; }
interface B { public function bar(): string; }

class C implements A, B {
  public function foo(): string { return 'foo'; }
  public function bar(): string { return 'bar'; }
}

function test(A&B $obj) {
  echo $obj->foo() . ' ' . $obj->bar();
}

$c = new C();
test($c);

medium

A. foo bar

B. foo

C. bar

D. TypeError at runtime

Solution

1. Step 1: Understand class C implements both interfaces

   Class C implements both A and B, so it has methods foo() and bar().

2. Step 2: Call test with intersection type parameter

   Function test requires an object that is both A and B, which $c is. It calls foo() and bar() and echoes their results separated by space.

3. Final Answer:

   foo bar -> Option A

4. Quick Check:

   Object meets both interfaces, so output is 'foo bar' [OK]

Hint: Check if object implements all interfaces in intersection [OK]

Common Mistakes:

• Expecting only one method output
• Thinking intersection causes error if both interfaces implemented
• Confusing union with intersection types

4. What is the error in this code snippet?

interface X { public function x(): void; }
interface Y { public function y(): void; }

function example(X&Y $obj) {
  $obj->x();
  $obj->y();
}

class Z implements X {
  public function x(): void {}
}

$z = new Z();
example($z);

medium

A. No error, code runs fine.

B. TypeError because $z does not implement interface Y.

C. Syntax error in function declaration.

D. Fatal error: method y() not found in class Z.

Solution

1. Step 1: Check class Z interfaces

   Class Z implements only interface X, not Y.

2. Step 2: Analyze function parameter type

   Function example requires an object implementing both X and Y (intersection). Passing $z violates this.

3. Final Answer:

   TypeError because $z does not implement interface Y. -> Option B

4. Quick Check:

   Intersection requires all interfaces, missing one causes TypeError [OK]

Hint: All interfaces in intersection must be implemented [OK]

Common Mistakes:

• Assuming partial interface implementation is enough
• Confusing syntax error with type error
• Thinking missing method causes fatal error instead of TypeError

5. You want to write a function that accepts an object which must be both JsonSerializable and Countable. You also want to ensure the object has a method customMethod(). Which of the following is the best way to type hint this in PHP 8.1+?

hard

A. function process(JsonSerializable|Countable $obj) { $obj->customMethod(); }

B. function process(JsonSerializable&Countable&CustomInterface $obj) {}

C. function process(object $obj) { $obj->customMethod(); }

D. function process(JsonSerializable&Countable $obj) { if (method_exists($obj, 'customMethod')) { $obj->customMethod(); } }

Solution

1. Step 1: Understand intersection type usage

   Use & to require both JsonSerializable and Countable interfaces.

2. Step 2: Handle custom method not in interfaces

   Since customMethod() is not part of these interfaces, check its existence with method_exists before calling.

3. Final Answer:

   function process(JsonSerializable&Countable $obj) { if (method_exists($obj, 'customMethod')) { $obj->customMethod(); } } -> Option D

4. Quick Check:

   Intersection + runtime check for extra method [OK]

Hint: Use & for interfaces and method_exists for extra methods [OK]

Common Mistakes:

• Using union (|) instead of intersection (&)
• Assuming method in interfaces without checking
• Ignoring type safety by using object without interfaces