From: matz@... Date: 2020-02-27T08:23:33+00:00 Subject: [ruby-core:97288] [Ruby master Bug#9573] descendants of a module don't gain its future ancestors, but descendants of a class, do Issue #9573 has been updated by matz (Yukihiro Matsumoto). The patch for `include` looks OK to me. To ensure there are no unseen compatibility issues, I'd like to experiment with it during the 2.8 development cycle. I am not yet sure how `prepend` should work here. I need to think about it more deeply. Keep it as it is for `prepend` for the moment. Matz. ---------------------------------------- Bug #9573: descendants of a module don't gain its future ancestors, but descendants of a class, do https://bugs.ruby-lang.org/issues/9573#change-84406 * Author: rits (First Last) * Status: Open * Priority: Normal * ruby -v: ruby 2.1.1p76 (2014-02-24 revision 45161) [i686-linux] ---------------------------------------- ```ruby module Mod1 end module Mod2 end class Class1 end class Class2 < Class1 end p Class2.ancestors - Object.ancestors # [Class2, Class1] Class1.include Mod1 p Class2.ancestors - Object.ancestors # [Class2, Class1, Mod1] Mod1.include Mod2 p Mod1.ancestors - Object.ancestors # [Mod1, Mod2] p Class2.ancestors - Object.ancestors # [Class2, Class1, Mod1] ``` ________________________________________________________________ note that descendants of a class do gain its future ancestors so 2 issues: 1. It would seem natural that in dynamic language, dynamically added ancestors should propagate to descendants 2. Why is there a difference in ancestor propagation between modules and classes ---Files-------------------------------- include-future-ancestors-9573.patch (3.49 KB) prepend-future-ancestors-9573.patch (6.42 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>