Bug #12594: The class does not inherit from a module the modules that were included after the inclusion

• Status: Closed
• Assignee: nobu (Nobuyoshi Nakada)
• Target version: -
• ruby -v: 2.3.0, 2.3.1
• Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
• Tags: core, notbug

[faucct (Nikita Sokolov)]

Reproduced in ruby 2.3.0 and 2.3.1
You can see that the result changes if I swap places LimitedPeriod.include Period and Period.include Serialization.

module Serialization
end

module Period
end

Period.include Serialization

class LimitedPeriod
  include Period
end

LimitedPeriod < Serialization
# => true

module Serialization
end

module Period
end

class LimitedPeriod
  include Period
end

Period.include Serialization

LimitedPeriod < Serialization
# => false

[faucct (Nikita Sokolov)]

• Description updated (diff)

[shyouhei (Shyouhei Urabe)]

I listed this issue to be looked at the yesterday's developer meeting but sadly no time was there to deeply inspect it. At a glance it seems possible now to reflect inclusion happened afterwards. It has a chance.

[shyouhei (Shyouhei Urabe)]

• Status changed from Open to Assigned
• Assignee set to nobu (Nobuyoshi Nakada)

We at developer meeting looked at it again. Nobu thinks he can fix this so I'm assigning to him. He said to me this is low priority, though.

[jeremyevans0 (Jeremy Evans)]

• Status changed from Assigned to Closed

This was implemented in 3556a834a2847e52162d1d3302d4c64390df1694.