Bang methods (ending with !) in Ruby - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does a bang method (ending with !) indicate in Ruby?

A bang method usually means it performs a more "dangerous" or "destructive" action, often modifying the object it is called on instead of returning a new object.

beginner

Example: What is the difference between upcase and upcase! methods on a string?

upcase returns a new string with all uppercase letters, leaving the original string unchanged. upcase! changes the original string itself to uppercase and returns nil if no changes were made.

intermediate

Does every bang method modify the object it is called on?

Usually yes, but not always. Bang methods often modify the object, but the main idea is that they are "dangerous" or have side effects compared to their non-bang counterparts.

beginner

What does gsub vs gsub! do on a string?

gsub returns a new string with replacements, leaving the original unchanged. gsub! modifies the original string in place and returns nil if no replacements were made.

beginner

Why should you be careful when using bang methods?

Because they can change the original object, which might cause unexpected bugs if you rely on the original data elsewhere in your program.

What does a bang method (ending with !) usually do in Ruby?

A Modifies the object it is called on

B Returns a new object without changing the original

C Always raises an error

D Is slower than non-bang methods

Bang methods usually modify the object they are called on, unlike their non-bang versions which return new objects.

What will str.upcase! return if str is already uppercase?

A false

B The uppercase string

C An error

D nil

If no changes are made, bang methods like upcase! return nil.

Which method modifies the original string in place?

A upcase

B gsub

C gsub!

D downcase

gsub! modifies the original string, while gsub returns a new string.

Are all bang methods guaranteed to modify the object?

A Yes, always

B No, but usually

C No, never

D Only if the object is a string

Bang methods usually modify the object but the main idea is that they are more "dangerous" or have side effects.

Why might you avoid using bang methods carelessly?

A They can cause unexpected changes to data

B They always raise exceptions

C They don't work on arrays

D They are slower

Bang methods can change the original object, which might cause bugs if you expect the original data to stay the same.

Explain what a bang method is in Ruby and how it differs from its non-bang counterpart.

Think about how the method changes the object it is called on.

Give an example of a bang method on strings and describe what happens when you use it.

Consider how the string changes after calling the method.

Practice

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