How to use return statement

return.rb

# One return per line makes it easy to understand / debug
def done?
  return false if no_one_done_it?
  return false if not_found?
  return true  if you_did_it?
  false
end

# Special case pattern (!= NullObject)
# Some, including Kent Beck and Martin Fowler argue that one or more guard clauses
# -- conditional "early exit" return statements near the beginning of a function --
# often make a function easier to read than the alternative.
def do_it
  return unless @go_for_it

  # code with no other early return
  # implicit return
end

# Default
# Single Entry, Single Exit (SESE)
# It's the best because it's the simplest flow (*)
# Also, when return is used to "return early", it may suffer from the same sort
# of problems that arise for the GOTO statement.
def make
  prepare_make

  if shouldnt_be_made?
    false
  elsif can_be_make_easily?
    simply_make_it! # => [true|false]
  else
    try_to_make_it! # => [true|false]
  end
end

# The case for node (super-nested code):
# Conversely, it can be argued that using the return statement is worthwhile
# when the alternative is more convoluted code, such as deeper nesting, harming readability.

# * Conditions apply

# In the sources:
# http://en.wikipedia.org/wiki/Return_statement