Community
Participate
Working Groups
This is a proposal as well as a discussion based on suggestions made as part of Igor's POC in https://github.com/ifedorenko/jdt-indexer-musings . Certain parts of it are probably a no-go for now (eg. rocksdb adoption) but exploring small changes to the indexer format that may yield performance benefits seems worth it. - Add class information for the given method reference (eg. a key of toString/0 becomes toString/0/java.lang.Object ) and using class hierarchy information to also include method references of sub-classes. I've been playing around with a relatively small patch that does this but am working through how to fetch the hierarchy information more efficiently.
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.
