vscode-cpptools
vscode-cpptools copied to clipboard
microsoft
Call hierarchy
Perhaps the inverse to #15; to be able to view an entire call hierarchy of a function.
Seen it implemented in Eclipse.
Having this feature would be awesome! In Eclipse it also works for class fields, enum constants and global variables (showing functions they're used in, and expanding the function call hierarchy from there). To be better than Eclipse, making it work for macros as well would be extra cool :)
It's really invaluable to understand and navigate non-small code bases.
Visual Studio has this, but VS Code doesn't currently have any interface to enable a call hierarchy (other than possibly some unusual interface involving repeated dropdown popups). Maybe someone could file a feature request with VS Code to enable this, if it's not already been requested? This would require the IntelliSense engine from our end. It's not on our radar to implement this yet though (Find All References would be higher priority).
Adding my vote to this one. This would be my number 1 most important missing feature and use it daily in eclipse to navigate and understand the structure of a large code base. I can live without find all references feature and use global text search with whole word option instead.
A new tree view api has been added to vscode. So, this should be doable now.
Looks like https://code.visualstudio.com/docs/extensionAPI/vscode-api#TreeDataProvider .
Can I vote twice for this one? The well implemented call hierarchy is the main reason eclipse is still my go-to IDE as its an invaluable tool to navigate 1M+ LOC code bases.
I would also appreciate this feature. Highly used feature... I finally could switch from eclipse to Visual code.
@KarolisMil Yes, this is our second most up-voted feature request (behind find all references). Survey feedback indicates that too many users are having trouble getting IntelliSense setup so we're working on improving that first.
@iradiohead No news. We haven't started working on this yet. We plan to implement IntelliSense-based Go to Definition and Find All References before a Call Hierarchy, all of which requires implementing a multi-translation unit IntelliSense (our currently one is only one translation unit at a time).
waiting for this feature. Daily waste like an hour because of absence of this feature!!
This is now third on the feature backlog. I don't have a date for you yet though.
Great news! I am hoping its going to be similar to Eclipse's call hierarchy where a button lets you select if it's caller or callee [1] (though I rarely look up callees). Unlike [2]. However, like [2] would be great if we could have a code definition window where a preview is displayed for the selected item. This helps avoid context switching in the main editor.
[1] https://help.eclipse.org/mars/topic/org.eclipse.cdt.doc.user/images/view_call_hierarchy.png [2] https://docs.microsoft.com/en-us/visualstudio/ide/reference/call-hierarchy?view=vs-2017,
Like Eclipse, XCode, PyCharm, whatever... this is absolutely needed in any serious professional programming environment Just find myself to switch back to XCode on my mac right now because I need to see a big project call tree... sigh...
This would be great to enable in cpptools extension!
https://code.visualstudio.com/updates/v1_33#_call-hierarchy
The Call hierarchy/Find references/Peek references can't work in VS code. I found this issue was first reported at 2016, can we have this function now? This is a very useful feature in DEV tool~
This was in the Sept 2019 milestone: "@sean-mcmanus sean-mcmanus added this to the September 2019 milestone on Apr 3" and now back on deck - what's needed to prioritize this sooner?
This is the 3rd most voted feature, but I don't think it made our cut for milestone scheduling purposes, because we have other stuff we're prioritizing like localization, non-UTF-8 support, make support, cmake support. In particular, we want to improve our infrastructure and code sharing with VS so that we can share a common call hierarchy implementation (and other features) instead of wasting time writing our own implementation that might get thrown away later (e.g. like what we're doing for Find All References). @bobbrow Might be able to explain better?