[ruby-core:23741] [Feature #1586] Including a module already present in ancestors should not be ignored

Issue #1586 has been updated by Rick DeNatale.


Actually, for a while, back in 2006, Ruby 1.9 (in its experimental form) used to do just what this ticket asks for:

http://talklikeaduck.denhaven2.com/2006/10/09/a-subtle-change-to-mixin-semantics-in-ruby-1-9

However, that change got reverted.

I asked Matz why at RubyConf 2007, and documented our conversion

http://talklikeaduck.denhaven2.com/2007/11/03/a-chat-with-matz-classs-variable-reversion-and-a-mystery-explained

The problem is that MRI, and I guess YARV doesn't keep track of where in the chain of classes, and module proxies it found the currently executing method, so super is implemented by doing a method search starting with the klass of self, and proceding until the method is found a SECOND time.  With this implementation it's easier to turn module re-inclusion into a nop than to deal with the consequences.


----------------------------------------
http://redmine.ruby-lang.org/issues/show/1586

----------------------------------------
http://redmine.ruby-lang.org