In Rust, Java, and similar languages, method names like new(), run(), or Dispose() collide frequently across unrelated types. This creates a spaghetti graph effect during traversal.
Ideas
- Prefer qualified labels in traversal output when collisions exist
- Add a show only qualified labels query option
- Append source file or parent module to ambiguous nodes in output
- Extract static receiver/type hints from tree-sitter (e.g., impl Foo automatically gives Foo::new)
Acceptance
- Query output is measurably less ambiguous for colliding labels
- No breaking change to graph.json schema
In Rust, Java, and similar languages, method names like new(), run(), or Dispose() collide frequently across unrelated types. This creates a spaghetti graph effect during traversal.
Ideas
Acceptance