Object#dup and Object#clone in Ruby - Time & Space Complexity

Time Complexity: Object#dup and Object#clone

O(n)

Understanding Time Complexity

When we use dup or clone in Ruby, we create copies of objects. Understanding how long this copying takes helps us write faster programs.

We want to know: how does the time to copy grow as the object gets bigger or more complex?

Scenario Under Consideration

Analyze the time complexity of the following Ruby code snippet.

obj = [1, 2, 3, 4, 5]
copy1 = obj.dup
copy2 = obj.clone
    

This code creates two copies of an array object using dup and clone.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: copying each element inside the object (array) one by one
• How many times: once for each element in the array

How Execution Grows With Input

As the object gets bigger, copying takes longer because each element must be copied.

Input Size (n)	Approx. Operations
10	About 10 element references copied
100	About 100 element references copied
1000	About 1000 element references copied

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

Final Time Complexity

Time Complexity: O(n)

This means copying takes time proportional to the size of the object being copied.

Common Mistake

[X] Wrong: "Copying an object is always instant and does not depend on its size."

[OK] Correct: Copying must handle each part of the object, so bigger objects take more time.

Interview Connect

Knowing how copying objects scales helps you explain performance in real programs. It shows you understand what happens behind the scenes when you duplicate data.

Self-Check

"What if the object contains other objects that also need to be copied? How would that affect the time complexity?"