mirror of
https://github.com/qdrant/qdrant.git
synced 2026-09-21 13:37:46 -05:00
Andrey VasnetsovandClaude Fable 5.1
29e21bea96
rust-analyzer's call hierarchy is function-only, so a type root is walked via find-references instead: each mention is attributed to its enclosing document symbol (function, type definition, or impl block's self type), and a type's callees are its methods. Type nodes are square; new edge kinds `ref` and `member` get their own labels and legend entries. Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
callgraph
Interactive call-graph reports for one function or type of the Qdrant workspace, viewable in a browser: pan/zoom graph, per-node docs and source snippets, exact call sites, GitHub/editor links.
tools/callgraph/callgraph.py read_bytes_async # by name
tools/callgraph/callgraph.py universal_io::traits::read_bytes_async # :: segments disambiguate
tools/callgraph/callgraph.py lib/common/common/src/universal_io/traits/read.rs:113
tools/callgraph/callgraph.py common::universal_io::traits::append::UniversalAppendFs # trait/struct/enum/type/const
Prints a file://…/target/callgraph/<fn>.html link when done. Requires
rust-analyzer and graphviz dot on PATH; no Python dependencies.
How it works
- rust-analyzer's call hierarchy over LSP provides resolved (not textual) caller/callee edges; both directions are collected in one run.
- Trait declarations and their impls are bridged via goto-implementation / goto-declaration, so a walk doesn't dead-end when a call dispatches through a trait (dashed edges in the graph).
- The call hierarchy is function-only, so a struct/trait root is walked via find-references instead: each mention is attributed to its enclosing function, or — for mentions in type definitions and impl headers — to the enclosing type / the impl block's self type (square nodes, teal edges). A type's "callees" are its methods (trait body + impl blocks, dotted edges).
- Test code is excluded for real: rust-analyzer runs with
cfg(test)off, andtests/,benches/,examples/targets are filtered by path. - Layout by graphviz at generation time; the report itself is one self-contained HTML file with no external resources.
Options
--depth N— call hops from the root (default 4)--max-nodes N— per-view node cap (default 250)--out PATH— output HTML path
Performance note
Each run cold-starts rust-analyzer, which re-indexes the workspace (~3 min).
If runs become frequent, the upgrade path is a --serve mode that keeps one
rust-analyzer instance alive between reports.