Intersection types in practice in PHP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a function that accepts an argument implementing both LoggerInterface and JsonSerializable.

PHP

<?php
function logData([1] $data): void {
    // function body
}
?>

Drag options to blanks, or click blank then click option'

AJsonSerializable

BLoggerInterface|JsonSerializable

CLoggerInterface&JsonSerializable

DLoggerInterface

Attempts:

3 left

💡 Hint

Common Mistakes

Using | instead of & for intersection types

Specifying only one interface

The intersection type LoggerInterface&JsonSerializable ensures the argument implements both interfaces.

2fill in blank

medium

Complete the code to declare a class that implements both Countable and IteratorAggregate using intersection types in a method parameter.

PHP

<?php
class Collection {
    public function process([1] $item): void {
        // process item
    }
}
?>

Drag options to blanks, or click blank then click option'

ACountable&IteratorAggregate

BCountable

CCountable|IteratorAggregate

DIteratorAggregate

Attempts:

3 left

💡 Hint

Common Mistakes

Using | instead of &

Using only one interface

The parameter type Countable&IteratorAggregate requires the argument to implement both interfaces.

3fill in blank

hard

Fix the error in the function parameter type declaration to correctly use intersection types.

PHP

<?php
function handle([1] $obj): void {
    // handle object
}
?>

Drag options to blanks, or click blank then click option'

ATraversable&Countable

BTraversable|Countable

CTraversable

DCountable

Attempts:

3 left

💡 Hint

Common Mistakes

Using | instead of &

Using only one interface

Intersection types use & to require the argument to implement both interfaces.

4fill in blank

hard

Fill both blanks to create a function that accepts an argument implementing both ArrayAccess and JsonSerializable, and returns a string.

PHP

<?php
function exportData([1] $data): [2] {
    return json_encode($data);
}
?>

Drag options to blanks, or click blank then click option'

AArrayAccess&JsonSerializable

Bstring

Cint

DArrayAccess|JsonSerializable

Attempts:

3 left

💡 Hint

Common Mistakes

Using | instead of &

Wrong return type

The parameter uses intersection type ArrayAccess&JsonSerializable and the return type is string.

5fill in blank

hard

Fill all three blanks to define a function that accepts an argument implementing both Countable and IteratorAggregate, returns an int, and uses a variable to store the count.

PHP

<?php
function countItems([1] $collection): [2] {
    $count = count($collection);
    return [3];
}
?>

Drag options to blanks, or click blank then click option'

ACountable&IteratorAggregate

Bint

C$count

DCountable|IteratorAggregate

Attempts:

3 left

💡 Hint

Common Mistakes

Using | instead of &

Returning wrong variable or type

The parameter uses intersection type Countable&IteratorAggregate, the return type is int, and the function returns the variable $count.

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