[ruby-core:28783] [Feature #2065] An ancestors iterator

Issue #2065 has been updated by Simon Chiang.


So to clarify...  How much any piece of code of a bottleneck depends on how frequently the code gets run, and that is application-specific.  In my own application, it IS enough of a bottleneck for me to make this request because I run the code very frequently.  In other applications, it may not be a bottleneck.

For DSLs that want to have method-like inheritance, the lack of an ancestors iterator is a potential and unnecessary bottleneck.  An each_ancestor iterator would, as per the benchmarks, significantly speed up a useful programming pattern that I think would be used more frequently if it were inherently faster. I hope that clarifies the purpose of this request.

Using superclass would work in the example I gave you but not in general because as I understand it superclass does not visit modules.  Using ancestors allows for method-like 'inheritance' because you can visit both modules and superclasses. Using superclass limits you to the class hierarchy. 


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

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