Add incoming_calls and outgoing_calls tools #38
Conversation
| // After this point we just return errors instead of erroring out | ||
| var result strings.Builder | ||
|
|
||
| for _, symbol := range results { |
There was a problem hiding this comment.
For this tool it might be better to accept an exact location instead of a name, sort of like how hover works. The reason I say this is because "definition" is currently pretty imprecise, especailly in larger projects. If it is based on a location then it could be called after a first call to find out where the desired symbol is.
There was a problem hiding this comment.
Maybe?
In my initial experiments, I'm not sure adding these calls is actually useful anyways. For some projects the output is really large because the LLM isn't setting depth. I noticed that without this it would use references to basically do the same thing.
There was a problem hiding this comment.
do you mean you're not sure if these call_hierarchy tools are useful?
In my experience, it already works really well if you instruct the LLM to recursively look up definitions that are relevant to a specific code flow you're interested in. This way it only looks things up that are relevant.
No description provided.