Symbol clustering #198
Closed
Symbol clustering #198
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Patch is upstreamed in the ODB-2.5.0 working trunk, but a 2.5.0 version does not exist yet.
This change improves the resolution of "jump to definition" and "get usages"-like queries by enhancing accuracy from linkage information. Symbols which are static-linked together to a query are shown in bold green, symbol that aren't will be grey. Therefore, users can better choose which "definition" a call site is referring to better, for large projects. Signed-off-by: Szalay Richárd <szalayrichard@inf.elte.hu>
…link commands are found
whisperity
force-pushed
the
symbol-clustering
branch
from
692a736 to
6652380
Compare
whisperity
added
the
Plugin: C++
Collaborator
|
Closing this pull request as there have been no activity on it in a long time, and no review have been performed for some reason. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduce the symbol clustering algorithm and improvements to CodeCompass. This change makes CodeCompass use the linkage information available in the
build.json(if present), to store linkage data to certain translation units in a quick and optimalised manner.This data is used when the user is searching between symbols (such as Jump to Definition or List Callees queries) to generate the list of symbols that are statically linked to the "search origin" (e.g. the
f()call site). These results are highlighted (while those that are not statically link are highlighted in another way).With this change, if a project contains ambiguous mangled names, the user can easier select a definition that is supposedly (!) more relevant to the point where he/she is searching from, than other definitions matching based on the function signature.
This change produces minimal overhead in the database and has a minimal impact on parse and navigation time. The algorithm and the results has been discussed in detail on the 33rd Conference of Scientific Students' Associations (XXXIII. OTDK), and on the 17th IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM-2017).