Why is the included hook defined as a class method (self.included) rather than an instance method in Ruby modules?

hard📝 Conceptual Q10 of 15

Ruby - Advanced Metaprogramming

Why is the included hook defined as a class method (self.included) rather than an instance method in Ruby modules?

ABecause Ruby does not allow instance methods in modules

BBecause it needs to run when the module is included, not when instances are created

CBecause it modifies instance variables of the module

DBecause instance methods cannot be defined inside modules

Step-by-Step Solution

Solution:

Step 1: Understand when included hook runs
The included hook runs at the moment the module is included into a class or module, not when instances are created.
Step 2: Reason why it must be a class method
It must be a class method so Ruby can call it on the module itself during inclusion, before any instances exist.
Final Answer:
Because it needs to run when the module is included, not when instances are created -> Option B
Quick Check:
Included hook runs on module inclusion, so it's a class method [OK]

Quick Trick: Included hook runs on inclusion, so define as class method [OK]

Common Mistakes:

Master "Advanced Metaprogramming" in Ruby

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Ruby Quizzes