IteratorAggregate interface in PHP - Time & Space Complexity

Time Complexity: IteratorAggregate interface

O(n)

Understanding Time Complexity

When using the IteratorAggregate interface in PHP, we want to understand how the time to get items grows as the collection size grows.

We ask: How does looping through the items behave as the list gets bigger?

Scenario Under Consideration

Analyze the time complexity of this PHP code using IteratorAggregate.

class MyCollection implements IteratorAggregate {
    private array $items;
    public function __construct(array $items) {
        $this->items = $items;
    }
    public function getIterator(): Traversable {
        return new ArrayIterator($this->items);
    }
}

$n = 10; // example value for $n
$collection = new MyCollection(range(1, $n));
foreach ($collection as $item) {
    // process $item
}
    

This code creates a collection that can be looped over using IteratorAggregate, returning an iterator over an array of items.

Identify Repeating Operations

Look at what repeats when looping through the collection.

• Primary operation: Looping through each item in the array inside the iterator.
• How many times: Once for each item in the collection, so n times if there are n items.

How Execution Grows With Input

As the number of items grows, the loop runs once per item.

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

Pattern observation: The number of operations grows directly with the number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time to loop through the collection grows in a straight line with the number of items.

Common Mistake

[X] Wrong: "Using IteratorAggregate makes looping slower because it adds extra steps."

[OK] Correct: The interface just provides a way to get the iterator; the main work is still looping through each item once, so the time grows linearly.

Interview Connect

Understanding how interfaces like IteratorAggregate affect performance helps you explain your code choices clearly and shows you know how data size impacts speed.

Self-Check

"What if the getIterator method returned a generator instead of an ArrayIterator? How would the time complexity change?"

Practice

1.

What is the main purpose of the IteratorAggregate interface in PHP?

easy

A. To allow an object to be iterated with foreach by providing an external iterator.

B. To automatically sort arrays inside an object.

C. To enforce type checking on array elements.

D. To convert an object into a string representation.

Solution

1. Step 1: Understand the role of IteratorAggregate

   The interface requires implementing getIterator() which returns an iterator object.

2. Step 2: Connect to foreach usage

   This allows the object to be used in foreach loops by providing the iterator externally.

3. Final Answer:

   To allow an object to be iterated with foreach by providing an external iterator. -> Option A

4. Quick Check:

   IteratorAggregate enables foreach iteration [OK]

Hint: Remember: IteratorAggregate provides an iterator for foreach [OK]

Common Mistakes:

• Thinking it sorts data automatically
• Confusing it with string conversion
• Assuming it enforces type checks

2.

Which method must a class implement when it uses the IteratorAggregate interface?

easy

A. getItems()

B. iterate()

C. getIterator()

D. toArray()

Solution

1. Step 1: Recall interface requirements

   The IteratorAggregate interface requires the getIterator() method.

2. Step 2: Confirm method name

   This method must return an iterator object to enable iteration.

3. Final Answer:

   getIterator() -> Option C

4. Quick Check:

   IteratorAggregate requires getIterator() [OK]

Hint: Interface method is always getIterator() [OK]

Common Mistakes:

• Using iterate() instead of getIterator()
• Confusing with toArray() method
• Assuming getItems() is required

3.

What will be the output of this PHP code?

<?php
class MyCollection implements IteratorAggregate {
    private array $items = [1, 2, 3];
    public function getIterator(): Traversable {
        return new ArrayIterator($this->items);
    }
}

$collection = new MyCollection();
foreach ($collection as $item) {
    echo $item . ' ';
}

medium

A. ArrayIterator Object

B. 1 2 3

C. Error: getIterator must return array

D. No output

Solution

1. Step 1: Understand getIterator() return

   The method returns an ArrayIterator over the array [1, 2, 3].

2. Step 2: foreach loops over iterator

   The foreach loop iterates over the items 1, 2, and 3, echoing each with a space.

3. Final Answer:

   1 2 3 -> Option B

4. Quick Check:

   foreach prints each item from ArrayIterator [OK]

Hint: getIterator returns ArrayIterator to enable foreach [OK]

Common Mistakes:

• Expecting an error because getIterator returns ArrayIterator
• Thinking it prints object instead of values
• Missing the space after each number

4.

Identify the error in this PHP class implementing IteratorAggregate:

<?php
class Numbers implements IteratorAggregate {
    private array $nums = [10, 20, 30];
    public function getIterator() {
        return $this->nums;
    }
}

medium

A. getIterator() must return an object implementing Traversable, not an array.

B. Property $nums should be public, not private.

C. Class must implement Iterator, not IteratorAggregate.

D. getIterator() method must be static.

Solution

1. Step 1: Check getIterator() return type

   It returns an array, but getIterator() must return an object implementing Traversable.

2. Step 2: Understand interface contract

   Returning an array causes a type error because arrays do not implement Traversable.

3. Final Answer:

   getIterator() must return an object implementing Traversable, not an array. -> Option A

4. Quick Check:

   getIterator() returns Traversable object [OK]

Hint: getIterator must return Traversable object, not array [OK]

Common Mistakes:

• Returning array directly from getIterator()
• Thinking private properties cause error here
• Assuming getIterator() must be static

5.

You want to create a class FilteredCollection that implements IteratorAggregate and only iterates over items greater than 5 from an internal array. Which implementation of getIterator() is correct?

<?php
class FilteredCollection implements IteratorAggregate {
    private array $items;
    public function __construct(array $items) {
        $this->items = $items;
    }
    public function getIterator(): Traversable {
        // Which code below is correct?
    }
}

hard

A. return new ArrayIterator($this->items);

B. return new ArrayIterator(array_map(fn($v) => $v > 5, $this->items));

C. return $this->items;

D. return new ArrayIterator(array_filter($this->items, fn($v) => $v > 5));

Solution

1. Step 1: Filter items greater than 5

   Use array_filter with a callback to keep only values > 5.

2. Step 2: Return an ArrayIterator over filtered items

   Wrap filtered array in ArrayIterator to satisfy Traversable return type.

3. Final Answer:

   return new ArrayIterator(array_filter($this->items, fn($v) => $v > 5)); -> Option D

4. Quick Check:

   Filter then wrap in ArrayIterator [OK]

Hint: Filter array first, then return ArrayIterator [OK]

Common Mistakes:

• Returning unfiltered array directly
• Using array_map instead of array_filter
• Not wrapping result in an iterator object