Object identity (equal? vs ==) in Ruby - Quick Revision & Key Differences

Recall & Review

beginner

What does the equal? method check in Ruby?

The equal? method checks if two variables point to the exact same object in memory. It tests object identity.

beginner

What does the == operator check in Ruby?

The == operator checks if two objects have the same value or content, not necessarily the same object in memory.

beginner

Given a = "hello" and b = "hello", what will a.equal?(b) return?

It will return false because a and b are two different string objects even though they have the same content.

beginner

Given a = "hello" and b = "hello", what will a == b return?

It will return true because a and b have the same string content.

intermediate

Why might you use equal? instead of ==?

Use equal? when you want to know if two variables are exactly the same object, not just equal in value. This is important when object identity matters.

In Ruby, which method checks if two variables refer to the same object?

A equal?

B ==

C eql?

D equals

The equal? method checks if two variables point to the exact same object in memory.

What does a == b check in Ruby?

A If a and b are the same object

B If a and b have different object ids

C If a and b have the same value

D If a and b are different classes

The == operator checks if two objects have the same value or content.

If a = "cat" and b = a, what will a.equal?(b) return?

A true

B false

C nil

D error

Since b points to the same object as a, equal? returns true.

Which method would return false for two different string objects with the same content?

A clone

B ==

C to_s

D equal?

equal? returns false because the objects are different, even if their content is the same.

What is the main difference between equal? and == in Ruby?

A <code>equal?</code> checks value, <code>==</code> checks identity

B <code>equal?</code> checks identity, <code>==</code> checks value

C Both check identity

D Both check value

equal? checks if two variables are the same object; == checks if their values are equal.

Explain the difference between equal? and == in Ruby with an example.

Think about whether two variables point to the same object or just have the same content.

When would you prefer to use equal? over == in your Ruby code?

Consider situations where knowing if two variables are exactly the same object matters.

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