Community
Participate
Working Groups
Extracted from bug 560139 comment 7: > I haven't tried, but from a quick look at the example, I guess the problem > is that "find references" is done for multiple equals and toString methods. > > Doing this kind of search even for a single method is very slow in Eclipse > (unless the search scope is small). IIRC Eclipse just has a simple text > index to find candidate classes that use methods with that method name at > all, and then parses and creates bindings for all the candidate classes > (which for equals and toString often means almost all classes that are in > the search scope)
Condition on JavaElementCodeMiningProvider L155 (just before minings.add(new JavaReferenceCodeMining(....)) can be refined to exclude the case of element being a field of Object.
@Henrik @Floris: this seems like an easy fix (see previous comment). Care to give it a try?
This is still a valid and good thing to implement.
Marking as ASSIGNED (to the jdt-inbox). This just indicates it has been triaged and deemed something worth pursuing should anyone find the time to work on it.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
