Why single inheritance in Ruby - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does Ruby use single inheritance?

Ruby supports only single inheritance. What is the main reason for this design choice?

A Because Ruby only allows inheritance from built-in classes

B Because Ruby does not support classes at all

C To force programmers to use only modules for all code reuse

D To keep the language simple and avoid complexity from multiple inheritance

💡 Hint

Think about how multiple inheritance can cause confusion in some languages.

Ruby uses single inheritance to keep the class hierarchy simple and avoid problems like the diamond problem that occur with multiple inheritance. Instead, Ruby uses modules to share code.

🧠 Conceptual

intermediate

How does Ruby achieve code reuse without multiple inheritance?

Since Ruby allows only single inheritance, how does it let programmers reuse code from multiple sources?

A By using modules and mixins to include shared behavior

B By copying code manually between classes

C By using multiple inheritance secretly behind the scenes

D By disallowing any code reuse

💡 Hint

Think about a way to add methods to a class without inheritance.

Ruby uses modules and mixins to add shared methods to classes. This allows code reuse without the complexity of multiple inheritance.

❓ Predict Output

advanced

Output of Ruby inheritance and module inclusion

What will be the output of this Ruby code?

Ruby

module M
  def greet
    "Hello from M"
  end
end

class A
  def greet
    "Hello from A"
  end
end

class B < A
  include M
end

puts B.new.greet

A Hello from M

B Hello from A

C NoMethodError

D SyntaxError

💡 Hint

Remember that included modules override methods from the superclass.

In Ruby, when a module is included in a class, its methods override those from the superclass. So B's greet method comes from module M.

❓ Predict Output

advanced

Method lookup order in Ruby with single inheritance and modules

What will this Ruby code print?

Ruby

module M1
  def info
    "M1"
  end
end

module M2
  def info
    "M2"
  end
end

class Parent
  def info
    "Parent"
  end
end

class Child < Parent
  include M1
  include M2
end

puts Child.new.info

A Parent

B M2

C M1

D NoMethodError

💡 Hint

The last included module has the highest priority in method lookup.

Ruby's method lookup checks the last included module first, so M2's info method is called.

🧠 Conceptual

expert

Why is multiple inheritance avoided in Ruby but allowed in some other languages?

Why does Ruby avoid multiple inheritance while languages like C++ allow it?

A Because Ruby does not support classes at all, only modules

B Because Ruby is an older language and never updated to support multiple inheritance

C To prevent complexity and ambiguity in method resolution, using modules instead for flexibility

D Because Ruby only supports inheritance from a single built-in class

💡 Hint

Think about the problems multiple inheritance can cause and how Ruby solves them differently.

Ruby avoids multiple inheritance to prevent issues like the diamond problem and method conflicts. Instead, it uses modules to mix in behavior, providing flexibility without complexity.