microsoft / microsoft/multilspy
CallHierarchy support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 610
- Forks
- 111
- PR merge metrics
- No merged PRs in 30d
Description
Hi there and thanks for creating multilspy!
I'm using it to create a language-agnostic-ish call graph to solve LLM code assistant context. [Article.]
Currently this is two passes:
- Forward pass through request_document_symbols to collect method regions
- For each symbol, call request_references and add edges
(1) is about 0.1s per file which is not great but I can live with it. But (2) is about 2.5s per source file.
Multithreading helps a little but not much (about a factor of 2x), because Python.
I think I could do (2) in request-per-file instead of request-per-symbol if I had CallHierarchy with outgoingCalls support.
WDYT?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing request_document_symbols and request_references APIs, then compare them with the Language Server Protocol CallHierarchy outgoingCalls capability. Done means multilspy exposes outgoing call hierarchy results so callers can request call edges per file rather than per symbol.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100