I avoid the use of 'Implementors' entirely as I always regret clicking on it because it takes such a long time in a large system with many classes. It would seem that it searches all classes for methods with the same name, rather than just showing the implementations in the current class hierarchy (inherited or from a subclass).
Perhaps it'd be better to review the behaviour of 'Implementors' to see if it should be changed to work like the description and/or performance improved, so the 'Local Implementors' can be left to just show subclass implementations (perhaps it'd be clearer to change the caption to reflect that though).
Nice idea, other than most of the time when I'm using Local Implementors it is because I specifically want to see only the implementations from that point downwards in the hierarchy. Having the current menu option also show superclass implementations would for me introduce noise I normally don't want into the results.
However, I can see times where it would be useful to be able to do an equivalent of "Local Implementors" in both directions. I wonder if a new "Implementors in Hierarchy"menu that shows both superclass and subclass implementations of the selected method would be less intrusive than changing the behaviour of the existing menu?
Guest
I avoid the use of 'Implementors' entirely as I always regret clicking on it because it takes such a long time in a large system with many classes. It would seem that it searches all classes for methods with the same name, rather than just showing the implementations in the current class hierarchy (inherited or from a subclass).
Perhaps it'd be better to review the behaviour of 'Implementors' to see if it should be changed to work like the description and/or performance improved, so the 'Local Implementors' can be left to just show subclass implementations (perhaps it'd be clearer to change the caption to reflect that though).
Nice idea, other than most of the time when I'm using Local Implementors it is because I specifically want to see only the implementations from that point downwards in the hierarchy. Having the current menu option also show superclass implementations would for me introduce noise I normally don't want into the results.
However, I can see times where it would be useful to be able to do an equivalent of "Local Implementors" in both directions. I wonder if a new "Implementors in Hierarchy" menu that shows both superclass and subclass implementations of the selected method would be less intrusive than changing the behaviour of the existing menu?