Readonly properties in PHP - Time & Space Complexity

Time Complexity: Readonly properties

O(n)

Understanding Time Complexity

Let's see how using readonly properties affects the time it takes for a PHP program to run.

We want to know how the program's steps grow when we use readonly properties in objects.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

class User {
    public readonly string $name;

    public function __construct(string $name) {
        $this->name = $name;
    }
}

$users = [];
for ($i = 0; $i < $n; $i++) {
    $users[] = new User("User" . $i);
}

This code creates $n User objects, each with a readonly name property set once during construction.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Creating a new User object and setting its readonly property.
• How many times: The loop runs exactly $n times, once per User object.

How Execution Grows With Input

Each new User object takes a fixed amount of time to create and set the readonly property.

Input Size (n)	Approx. Operations
10	About 10 object creations and property sets
100	About 100 object creations and property sets
1000	About 1000 object creations and property sets

Pattern observation: The work grows directly with the number of objects created.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line as we create more User objects with readonly properties.

Common Mistake

[X] Wrong: "Readonly properties make object creation instant or free."

[OK] Correct: Even though readonly properties cannot be changed later, setting them during construction still takes time for each object created.

Interview Connect

Understanding how readonly properties affect object creation helps you explain performance in real projects where immutability matters.

Self-Check

"What if we added a loop inside the User constructor that runs $m times? How would the time complexity change?"

Practice

1. What is the main purpose of readonly properties in PHP?

easy

A. To store values that cannot be changed after being set

B. To allow properties to be changed anytime

C. To make properties private

D. To automatically generate getter methods

Solution

1. Step 1: Understand readonly property behavior

   Readonly properties in PHP are designed to hold values that can only be assigned once and cannot be modified later.

2. Step 2: Compare options with this behavior

   To store values that cannot be changed after being set correctly describes this behavior, while others describe unrelated features.

3. Final Answer:

   To store values that cannot be changed after being set -> Option A

4. Quick Check:

   Readonly means unchangeable after set = A [OK]

Hint: Readonly means value set once and then fixed [OK]

Common Mistakes:

• Thinking readonly allows changes anytime
• Confusing readonly with private visibility
• Assuming readonly auto-generates methods

2. Which of the following is the correct syntax to declare a readonly property in a PHP class?

easy

A. readonly public int $id;

B. public readonly int $id;

C. public int readonly $id;

D. int public readonly $id;

Solution

1. Step 1: Recall PHP property declaration order

   In PHP, visibility (public/private/protected) comes first, then readonly keyword, then type and variable name.

2. Step 2: Match syntax with options

   public readonly int $id; matches the correct order: public readonly int $id;. Others have incorrect order.

3. Final Answer:

   public readonly int $id; -> Option B

4. Quick Check:

   Visibility then readonly then type = B [OK]

Hint: Visibility keyword comes before readonly in declaration [OK]

Common Mistakes:

• Placing readonly before visibility
• Putting readonly after type
• Mixing order of keywords

3. What will be the output of the following PHP code?

class User {
    public readonly string $name;
    public function __construct(string $name) {
        $this->name = $name;
    }
}
$user = new User('Alice');
echo $user->name;
$user->name = 'Bob';
echo $user->name;

medium

A. Alice followed by a fatal error

B. BobBob

C. AliceBob

D. Syntax error

Solution

1. Step 1: Understand readonly property assignment

   The readonly property $name is assigned once in the constructor to 'Alice'. This is allowed.

2. Step 2: Analyze second assignment

   Trying to assign $user->name = 'Bob'; after construction causes a fatal error because readonly properties cannot be changed after initial assignment.

3. Final Answer:

   Alice followed by a fatal error -> Option A

4. Quick Check:

   Readonly blocks changes after set = C [OK]

Hint: Readonly allows one assignment only, later changes cause error [OK]

Common Mistakes:

• Assuming readonly properties can be changed anytime
• Expecting no error on second assignment
• Confusing syntax error with runtime error

4. Identify the error in the following PHP code using readonly properties:

class Config {
    public readonly string $version;
    public function __construct() {
        $this->version = '1.0';
        $this->version = '2.0';
    }
}

medium

A. No error, code is correct

B. Missing visibility keyword for property

C. Readonly keyword used incorrectly with string type

D. Assigning readonly property twice in constructor

Solution

1. Step 1: Check property assignments in constructor

   The readonly property $version is assigned twice: first '1.0', then '2.0'.

2. Step 2: Understand readonly assignment rules

   Readonly properties can only be assigned once, even inside the constructor. Assigning twice causes an error.

3. Final Answer:

   Assigning readonly property twice in constructor -> Option D

4. Quick Check:

   Readonly assigned once only = A [OK]

Hint: Assign readonly property only once, even in constructor [OK]

Common Mistakes:

• Assigning readonly property multiple times
• Ignoring visibility keyword importance
• Thinking readonly disallows string type

5. Given this PHP class with readonly properties, which code correctly creates an immutable user with an ID and name?

class User {
    public readonly int $id;
    public readonly string $name;
    public function __construct(int $id, string $name) {
        $this->id = $id;
        $this->name = $name;
    }
}

Choose the correct usage:

hard

A. $user = new User(1, 'John'); $user->name = 'Jane';

B. $user = new User(1); $user->name = 'John';

C. $user = new User(1, 'John'); // no changes after construction

D. $user = new User(); $user->id = 1; $user->name = 'John';

Solution

1. Step 1: Check constructor usage

   The constructor requires two parameters: int $id and string $name. $user = new User(1, 'John'); // no changes after construction correctly calls the constructor with both.

2. Step 2: Verify immutability

   Readonly properties cannot be changed after construction. $user = new User(1, 'John'); // no changes after construction respects this by not modifying properties after creation.

3. Final Answer:

   $user = new User(1, 'John'); // no changes after construction -> Option C

4. Quick Check:

   Construct with all params, no changes after = D [OK]

Hint: Call constructor fully, then do not modify readonly properties [OK]

Common Mistakes:

• Trying to assign readonly properties after construction
• Calling constructor with missing arguments
• Assuming properties can be set without constructor