Inline vs Nested Ruby Module Declarations

building_up_module_declarations.sh

ruby -W2 -v -e '                                                                                                                                                                                     (ruby-2.2.2@benchprep) wip-simulation-endpoints 9a603b95e ✗
puts "before"
module Foo
  puts "- Foo -"
end

puts "more"
module Foo::Bar
  puts "- Foo::Bar -"
end

puts "and more"
module Foo::Bar::Baz
  puts "- Foo::Bar::Baz -"
end
puts "after"
'

# ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin14]
# before
# - Foo -
# more
# - Foo::Bar -
# and more
# - Foo::Bar::Baz -
# after

inline_module_declarations.sh

ruby -W2 -v -e '                                                                                                                                                                                     (ruby-2.2.2@benchprep) wip-simulation-endpoints 9a603b95e ✗
puts "before"
module Foo::Bar::Baz
  puts "Nope"
end
puts "after"
'

# ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin14]
# before
# -e:3:in `<main>': uninitialized constant Foo (NameError)

nested_module_declarations.sh

# Recommended
ruby -W2 -v -e '                                                                                                                                                                                     (ruby-2.2.2@benchprep) wip-simulation-endpoints 9a603b95e ✗
puts "before"
module Foo
  puts "- Foo -"
  module Bar
    puts "-- Bar -"
    module Baz
      puts "--- Baz -"
    end
    puts "-- Bar -"
  end
  puts "- Foo -"
end
puts "after"
'

# ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin14]
# before
# - Foo -
# -- Bar -
# --- Baz -
# -- Bar -
# - Foo -
# after

building_up_module_declarations.sh depends on the modules already being loaded which can sometimes be inconsistent depending on how the application is loaded. Safer to default with nested module so the module is defined automatically as needed.