Object identity (equal? vs ==) in Ruby - Performance Comparison

Time Complexity: Object identity (equal? vs ==)

O(1) for equal?, O(n) for ==

Understanding Time Complexity

When comparing objects in Ruby, we want to know how fast these checks run as the program grows.

We ask: How does the time to check object equality or identity change with input size?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

a = [1, 2, 3]
b = a
c = [1, 2, 3]

puts a.equal?(b)  # true
puts a.equal?(c)  # false
puts a == c       # true
puts a == b       # true

This code compares arrays using equal? and == to check identity and equality.

Identify Repeating Operations

• Primary operation: equal? checks if two variables point to the same object, which is a simple pointer check.
• Primary operation: == compares contents, which may involve checking each element in the array.
• How many times: equal? runs once per comparison, very fast.
• How many times: == may check each element, so it depends on array size.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations for ==
10	About 10 element checks
100	About 100 element checks
1000	About 1000 element checks

Pattern observation: equal? stays constant time no matter size, but == grows linearly with the number of elements.

Final Time Complexity

Time Complexity: O(1) for equal?, O(n) for ==

equal? is a quick check if two variables are the same object. == takes longer as it compares each element.

Common Mistake

[X] Wrong: "equal? and == always take the same time because they both compare objects."

[OK] Correct: equal? just checks if two things are the exact same object, which is very fast. == looks inside objects and compares each part, so it takes longer if the object is bigger.

Interview Connect

Understanding how object identity and equality checks work helps you write efficient code and explain your choices clearly in interviews.

Self-Check

"What if we compare nested arrays with ==? How would the time complexity change?"

Practice

1. In Ruby, what does the method equal? check between two objects?

easy

A. If both objects respond to the same methods

B. If both objects have the same content or value

C. If both variables point to the exact same object in memory

D. If both objects are of the same class

Solution

1. Step 1: Understand equal? method purpose

   The equal? method checks if two variables reference the exact same object in memory, not just if they look alike.

2. Step 2: Compare with other methods

   Unlike ==, which compares content, equal? is about object identity.

3. Final Answer:

   If both variables point to the exact same object in memory -> Option C

4. Quick Check:

   equal? checks object identity = D [OK]

Hint: Remember: equal? means same object, not just same value [OK]

Common Mistakes:

• Confusing equal? with ==
• Thinking equal? compares content
• Assuming equal? checks class type

2. Which of the following Ruby code snippets correctly uses equal? to check if two variables refer to the same object?

easy

A. a.equal?(b)

B. a == b

C. a.equals(b)

D. equal?(a, b)

Solution

1. Step 1: Recall correct syntax for equal?

   The method equal? is called on one object and passed another as an argument, like a.equal?(b).

2. Step 2: Identify incorrect options

   a == b uses content equality, a.equals(b) is not a Ruby method, and equal?(a, b) is invalid syntax.

3. Final Answer:

   a.equal?(b) -> Option A

4. Quick Check:

   Correct equal? syntax = B [OK]

Hint: Use object.equal?(other_object) syntax [OK]

Common Mistakes:

• Using == instead of equal?
• Writing equals instead of equal?
• Calling equal? as a standalone function

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

a = "hello"
b = "hello"
puts a == b
puts a.equal?(b)

medium

A. true
true

B. true
false

C. false
true

D. false
false

Solution

1. Step 1: Evaluate a == b

   Both a and b are strings with the same content "hello", so a == b returns true.

2. Step 2: Evaluate a.equal?(b)

   Though content is same, a and b are different string objects, so equal? returns false.

3. Final Answer:

   true false -> Option B

4. Quick Check:

   == compares content, equal? compares object identity = C [OK]

Hint: == checks value, equal? checks same object [OK]

Common Mistakes:

• Assuming equal? returns true for identical strings
• Confusing output order
• Thinking == checks object identity

4. Consider this Ruby code snippet:

arr1 = [1, 2, 3]
arr2 = arr1
arr3 = [1, 2, 3]

puts arr1.equal?(arr2)
puts arr1.equal?(arr3)

What is the output and why?

medium

A. false
false

B. false
true

C. true
true

D. true
false

Solution

1. Step 1: Analyze arr1.equal?(arr2)

   Since arr2 is assigned directly from arr1, both point to the same object, so equal? returns true.

2. Step 2: Analyze arr1.equal?(arr3)

   arr3 is a new array with the same content but a different object, so equal? returns false.

3. Final Answer:

   true false -> Option D

4. Quick Check:

   Same object = true, same content but different object = false [OK]

Hint: Assignment copies object reference; new array creates new object [OK]

Common Mistakes:

• Assuming arrays with same content are the same object
• Confusing == with equal?
• Thinking assignment creates a new object

5. You want to check if two variables x and y refer to the same object, but x might be nil. Which Ruby code safely performs this check without errors?

hard

A. x.equal?(y)

B. y.equals(x)

C. x&.equal?(y)

D. x == y

Solution

1. Step 1: Check safety of equal? on nil

   In Ruby, nil is an object and responds to equal?, so x.equal?(y) is safe even if x is nil. It returns false unless y is also nil.

2. Step 2: Eliminate distractors

   x&.equal?(y) returns nil if x is nil, which is not a proper boolean result. y.equals(x) calls a non-existent method. x == y checks content, not identity.

3. Final Answer:

   x.equal?(y) -> Option A

4. Quick Check:

   nil.equal?(y) safe boolean check = C [OK]

Hint: Even nil.equal?(other) works without error [OK]

Common Mistakes:

• Using &. which returns nil instead of boolean
• Calling non-existent equals method
• Using == which checks content, not identity