Bird
Raised Fist0
Rubyprogramming~5 mins

Bang methods (ending with !) in Ruby - Time & Space Complexity

Choose your learning style10 modes available
Time Complexity: Bang methods (ending with !)
O(n)
Understanding Time Complexity

We want to see how the time it takes to run bang methods changes as the input grows.

How does the cost of these methods grow when working with bigger data?

Scenario Under Consideration

Analyze the time complexity of the following Ruby code using a bang method.

arr = [1, 2, 3, 4, 5]
arr.reverse!
puts arr

This code reverses the array arr in place using the bang method reverse!.

Identify Repeating Operations

Look for loops or repeated steps inside the bang method.

  • Primary operation: The method swaps elements to reverse the array.
  • How many times: It swaps pairs of elements about half the array length times.
How Execution Grows With Input

As the array gets bigger, the number of swaps grows roughly in proportion to its size.

Input Size (n)Approx. Operations
10About 5 swaps
100About 50 swaps
1000About 500 swaps

Pattern observation: The work grows steadily as the array size grows, roughly doubling the work if the array size doubles.

Final Time Complexity

Time Complexity: O(n)

This means the time to reverse the array grows in a straight line with the size of the array.

Common Mistake

[X] Wrong: "Bang methods are always faster because they change data directly."

[OK] Correct: Bang methods change data in place but still do the same amount of work as their non-bang versions, so speed depends on the operation, not just the bang.

Interview Connect

Understanding how bang methods work and their time cost helps you explain your code choices clearly and confidently in real projects.

Self-Check

"What if we used reverse without the bang instead? How would the time complexity change?"

Practice

(1/5)
1. What is the main difference between a bang method (ending with !) and its non-bang counterpart in Ruby?
easy
A. Bang methods are slower than non-bang methods
B. Bang methods always return nil, non-bang methods return the object
C. Bang methods can only be used with strings
D. Bang methods modify the object itself, non-bang methods return a new object

Solution

  1. Step 1: Understand bang method behavior

    Bang methods (ending with !) usually change the original object directly.
  2. Step 2: Compare with non-bang methods

    Non-bang methods return a new object and leave the original unchanged.
  3. Final Answer:

    Bang methods modify the object itself, non-bang methods return a new object -> Option D
  4. Quick Check:

    Bang method = modifies object [OK]
Hint: Bang methods change the original object, non-bang do not [OK]
Common Mistakes:
  • Thinking bang methods return nil
  • Assuming bang methods only work on strings
  • Believing bang methods are slower
2. Which of the following is the correct syntax to use the bang method that reverses a string in Ruby?
easy
A. str.reverse!
B. str.reverse
C. str!reverse
D. reverse.str!

Solution

  1. Step 1: Recall Ruby method syntax

    Methods are called on objects using dot notation: object.method.
  2. Step 2: Identify the bang method for reversing

    The bang method for reversing a string is reverse!, so the correct call is str.reverse!.
  3. Final Answer:

    str.reverse! -> Option A
  4. Quick Check:

    Correct bang method syntax = str.reverse! [OK]
Hint: Bang methods use dot notation with ! at the end [OK]
Common Mistakes:
  • Placing ! before method name
  • Using wrong method call order
  • Omitting the dot between object and method
3. What will be the output of the following Ruby code?
arr = [1, 2, 3]
arr.reverse
puts arr.inspect
arr.reverse!
puts arr.inspect
medium
A. [1, 2, 3]\n[3, 2, 1]
B. [3, 2, 1]\n[1, 2, 3]
C. [1, 2, 3]\n[1, 2, 3]
D. [3, 2, 1]\n[3, 2, 1]

Solution

  1. Step 1: Understand arr.reverse effect

    arr.reverse returns a new reversed array but does not change arr itself, so arr.inspect prints the original: [1, 2, 3].
  2. Step 2: Understand arr.reverse! effect

    arr.reverse! reverses arr in place, changing it to [3, 2, 1]. So the second print shows [3, 2, 1].
  3. Final Answer:

    [1, 2, 3] [3, 2, 1] -> Option A
  4. Quick Check:

    Non-bang no change, bang changes object [OK]
Hint: Non-bang returns new object; bang changes original [OK]
Common Mistakes:
  • Assuming reverse changes original array
  • Confusing output order
  • Ignoring bang method effect
4. Consider this Ruby code snippet:
str = "Hello"
str.upcase
puts str
str.upcase!
puts str
What is the error in this code?
medium
A. No error; output is "HELLO" then "HELLO"
B. puts cannot print strings
C. Calling upcase without assignment does not change str
D. upcase! method does not exist

Solution

  1. Step 1: Analyze str.upcase call

    str.upcase returns an uppercase string but does not change str itself unless assigned.
  2. Step 2: Analyze str.upcase! call

    str.upcase! modifies str in place, changing it to uppercase.
  3. Final Answer:

    Calling upcase without assignment does not change str -> Option C
  4. Quick Check:

    Non-bang needs assignment to change object [OK]
Hint: Non-bang methods need assignment to change variable [OK]
Common Mistakes:
  • Thinking non-bang changes original string
  • Believing upcase! does not exist
  • Assuming puts can't print strings
5. You have an array of strings: words = ["apple", "banana", "Cherry"]. You want to convert all words to lowercase, modifying the original array directly. Which code correctly does this using bang methods?
hard
A. words.map { |w| w.downcase }
B. words.each { |w| w.downcase! }
C. words.each { |w| w.downcase }
D. words.map! { |w| w.downcase! }

Solution

  1. Step 1: Understand requirement to modify original array

    We want to change each string inside words directly, not create a new array.
  2. Step 2: Analyze each option

    • words.map! { |w| w.downcase! } uses map! with downcase!, but downcase! returns nil if no change, causing words to have nils.
    • words.map { |w| w.downcase } returns a new array, does not modify original.
    • words.each { |w| w.downcase } calls downcase but does not assign, so no change.
    • words.each { |w| w.downcase! } uses each with downcase!, modifying each string in place correctly.
  3. Final Answer:

    words.each { |w| w.downcase! } -> Option B
  4. Quick Check:

    Use each with bang method to modify elements [OK]
Hint: Use each with bang method to change elements in place [OK]
Common Mistakes:
  • Using map! with downcase! causing nils
  • Using non-bang methods without assignment
  • Using map without modifying original array
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard