Arithmetic operator overloading in Python - Time & Space Complexity

Time Complexity: Arithmetic operator overloading

O(n)

Understanding Time Complexity

When we use arithmetic operator overloading, we define how operators like + or * work with our own objects.

We want to see how the time needed changes as the size of the data inside these objects grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

class Vector:
    def __init__(self, values):
        self.values = values

    def __add__(self, other):
        return Vector([a + b for a, b in zip(self.values, other.values)])

v1 = Vector([1, 2, 3])
v2 = Vector([4, 5, 6])
v3 = v1 + v2
    

This code adds two vectors by adding their elements one by one.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The list comprehension loops through each pair of elements in the two vectors.
• How many times: It runs once for each element in the vectors, so as many times as the vector length.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10	About 10 additions
100	About 100 additions
1000	About 1000 additions

Pattern observation: The number of operations grows directly with the number of elements. Double the elements, double the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to add two vectors grows in a straight line with the size of the vectors.

Common Mistake

[X] Wrong: "Adding two vectors is always a fixed, quick operation no matter their size."

[OK] Correct: Actually, the time depends on how many elements are inside. Bigger vectors take more time because each element must be added.

Interview Connect

Understanding how operator overloading works and its time cost shows you can write clear code and think about efficiency, a skill useful in many coding challenges.

Self-Check

"What if we changed the vector addition to multiply each element instead? How would the time complexity change?"