Module declaration syntax in Ruby - Time & Space Complexity

Time Complexity: Module declaration syntax

O(n)

Understanding Time Complexity

Let's see how the time it takes to run code changes when we declare a module in Ruby.

We want to know how the work grows as the module size or content grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

module Greetings
  def hello
    puts "Hello!"
  end
end

class Person
  include Greetings
end

Person.new.hello

This code defines a module with one method, includes it in a class, and calls the method.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: There are no loops or repeated operations in this code.
• How many times: The method is called once, and module declaration happens once.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
1 method in module	Few operations to define and call
10 methods in module	About 10 times more operations to define
100 methods in module	About 100 times more operations to define

Pattern observation: The time to declare the module grows roughly in direct proportion to the number of methods inside it.

Final Time Complexity

Time Complexity: O(n)

This means the time to declare a module grows linearly with the number of methods it contains.

Common Mistake

[X] Wrong: "Declaring a module always takes the same time, no matter how many methods it has."

[OK] Correct: Each method inside the module adds work to define it, so more methods mean more time.

Interview Connect

Understanding how code size affects performance helps you write efficient Ruby programs and explain your reasoning clearly.

Self-Check

"What if the module included nested modules or classes? How would that affect the time complexity?"

Practice

1. What is the correct way to declare a module named MathTools in Ruby?

easy

A. def MathTools
# code here
end

B. module MathTools
# code here
end

C. class MathTools
# code here
end

D. package MathTools {
# code here
}

Solution

1. Step 1: Recognize Ruby module syntax

   In Ruby, modules are declared using the keyword module followed by the module name and end.

2. Step 2: Identify the correct declaration

   module MathTools # code here end uses module MathTools ... end, which is the correct syntax for a module.

3. Final Answer:

   module MathTools # code here end -> Option B

4. Quick Check:

   Ruby modules use module Name ... end [OK]

Hint: Modules start with 'module' and end with 'end' [OK]

Common Mistakes:

• Using 'class' instead of 'module'
• Using 'def' which is for methods
• Using non-Ruby syntax like 'package'

2. Which of the following is a syntax error when declaring a module in Ruby?

easy

A. module Tools {
def help
end
}

B. module Tools
def self.help
end
end

C. module Tools
end

D. module Tools
CONSTANT = 10
end

Solution

1. Step 1: Check Ruby module block delimiters

   Ruby modules use module ... end without braces { }.

2. Step 2: Identify invalid syntax

   module Tools { def help end } uses braces { } which is invalid syntax for module declaration in Ruby.

3. Final Answer:

   module Tools { def help end } -> Option A

4. Quick Check:

   Ruby modules use 'module ... end', not braces [OK]

Hint: Ruby modules never use curly braces for blocks [OK]

Common Mistakes:

• Using curly braces instead of 'end'
• Missing 'end' keyword
• Confusing module with class syntax

3. What will be the output of the following Ruby code?

module Greetings
  def self.say_hello
    "Hello!"
  end
end

puts Greetings.say_hello

medium

A. Hello!

B. Greetings.say_hello

C. NoMethodError

D. SyntaxError

Solution

1. Step 1: Understand module method definition

   The method say_hello is defined as a module method using self., so it can be called on the module directly.

2. Step 2: Evaluate the method call output

   Calling Greetings.say_hello returns the string "Hello!", which is printed by puts.

3. Final Answer:

   Hello! -> Option A

4. Quick Check:

   Module method call returns string output [OK]

Hint: Module methods use self. and can be called directly [OK]

Common Mistakes:

• Trying to call method without self. prefix
• Expecting instance method behavior
• Confusing syntax errors with method calls

4. Identify the error in the following Ruby module declaration:

module Tools
  def help
    "Help message"
  end
end

Tools.help

medium

A. No error, code runs fine

B. Missing 'end' keyword for module

C. Method 'help' should be defined with 'self.' to call on module

D. Module name should be lowercase

Solution

1. Step 1: Check method definition inside module

   The method help is defined as an instance method, but called on the module directly.

2. Step 2: Understand method call context

   To call Tools.help, help must be a module method defined with self.help.

3. Final Answer:

   Method 'help' should be defined with 'self.' to call on module -> Option C

4. Quick Check:

   Module methods need 'self.' prefix to be called on module [OK]

Hint: Use 'def self.method' for module-level methods [OK]

Common Mistakes:

• Defining instance methods but calling on module
• Forgetting 'self.' prefix for module methods
• Assuming lowercase module names are valid

5. Given the following nested module declarations, which is the correct way to define a module Inner inside module Outer in Ruby?

module Outer
  # Your code here
end

hard

A. module Outer
class Inner
end
end

B. module Outer::Inner
end

C. module Outer.Inner
end

D. module Outer
module Inner
end
end

Solution

1. Step 1: Understand nested module syntax

   In Ruby, nested modules can be declared by placing one module inside another.

2. Step 2: Identify correct nested declaration

   module Outer module Inner end end correctly nests module Inner inside module Outer using indentation and end keywords.

3. Final Answer:

   module Outer module Inner end end -> Option D

4. Quick Check:

   Nested modules use nested 'module ... end' blocks [OK]

Hint: Nest modules by placing one inside another with 'module' [OK]

Common Mistakes:

• Using dot notation instead of :: for nested modules
• Using class instead of module for nested module
• Incorrect syntax like dot (.) in module names