Method naming conventions (? and ! suffixes) in Ruby - Step-by-Step Execution

Concept Flow - Method naming conventions (? and ! suffixes)

Define method

↓

Check method name suffix

↓

Returns boolean

↓

Use in condition

↓

End method call

Ruby methods ending with ? return true/false; methods ending with ! modify data or are 'dangerous'.

Execution Sample

Ruby

def empty?
  self.size == 0
end

def upcase!
  # modifies string in place
end

Shows a method with ? returning boolean and a method with ! modifying data.

Execution Table

Step	Method Called	Suffix	Behavior	Output/Effect
1	empty?	?	Returns boolean	true or false depending on condition
2	upcase!	!	Modifies object in place	String changed, returns modified string
3	empty?	?	Returns boolean	false if not empty
4	upcase!	!	Modifies object in place	String changed again
5	Call ends	-	-	Program continues

💡 Methods end after returning value or modifying object; suffix guides expected behavior.

Variable Tracker

Variable	Start	After empty? call	After upcase! call	After second upcase! call	Final
string	"hello"	"hello"	"HELLO"	"HELLO"	"HELLO"
empty_check	nil	false	false	false	false

Key Moments - 3 Insights

Why do methods end with a question mark?

Methods ending with ? always return true or false, signaling a yes/no answer, as shown in execution_table rows 1 and 3.

What does the exclamation mark mean in method names?

Methods ending with ! usually change the object itself or do something 'dangerous', as seen in execution_table rows 2 and 4 where the string is modified.

Can a method with ! suffix return a new object instead of modifying?

By convention, ! methods modify the object or have side effects; if it returns a new object, it should be documented clearly. The ! warns to use caution.

Visual Quiz - 3 Questions

Look at the execution_table at step 1, what type of value does the method ending with ? return?

A A boolean value (true or false)

B A modified string

C An integer

D Nothing (nil)

💡 Hint

Check the Behavior and Output/Effect columns in execution_table row 1.

At which step does the method with ! suffix modify the string variable?

A Step 1

B Step 3

C Step 2

D Step 5

💡 Hint

Look at execution_table rows with Method Called 'upcase!' and see the Output/Effect.

If the method empty? returned true at step 1, what would the string variable's size be?

A 1

B 0

C 5

D Cannot tell

💡 Hint

Refer to variable_tracker and the meaning of empty? returning true.

Concept Snapshot

Ruby method names ending with ? return true/false (boolean checks).
Methods ending with ! usually modify the object or perform 'dangerous' actions.
? methods are safe queries; ! methods warn to use with caution.
Use ? for predicates, ! for mutating or risky methods.
This naming helps understand method behavior at a glance.

Full Transcript

In Ruby, methods ending with a question mark (?) always return a boolean value, meaning true or false. This helps us quickly check conditions, like if a string is empty. Methods ending with an exclamation mark (!) usually change the object they are called on or do something that might be risky. For example, upcase! changes the string itself to uppercase. The question mark tells us the method is safe and just checks something, while the exclamation mark warns us to be careful because it changes data. The execution table shows calls to empty? returning true or false, and calls to upcase! modifying the string. The variable tracker shows how the string changes after upcase! calls. Remember, ? means 'asks a question' and returns true/false, ! means 'dangerous or modifies'. This naming helps us understand what methods do just by looking at their names.