feat: resolve Rust use declarations for cross-module and cross-crate calls
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Área
- developer-experience, tooling
Línea de trabajo
Start from docs/LANGUAGE-CAPABILITY-MATRIX.md line 176 and the Rust indexer code that extracts use declarations as dependency references; trace how module keys are computed at extract time and where the enclosing crate name is missing. Compare the same-file and same-computed-module-path resolution paths to see what a use-imported call needs. Confirm in openspec/specs/ that the deliberate-gap decision still holds, then add cross-module and cross-crate resolution plus tests for callers, callees, and impact.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What exists today?
The Rust indexer's handling of use declarations, which feeds call resolution.
How does it behave now?
use declarations are extracted as dependency references but never populate Imports (docs/LANGUAGE-CAPABILITY-MATRIX.md, line 176). A call through a use-imported name does not resolve across modules or crates. Only same-file and same-computed-module-path resolution succeeds.
The matrix gives the cause: the enclosing crate name is not available at extract time, so no matching module key is computed. The matrix also calls this gap deliberate. The maintainer must confirm whether that decision still holds.
The reporter did not attach command output.
How should it behave?
A call to helper, imported with use crate::util::helper;, resolves to the helper definition in module util. A call through use other_crate::helper; resolves to that crate's definition. Trait method resolution through a use import will work the same way.
What kind of improvement?
Correctness in an edge case
Would this change existing behavior?
Yes. Calls through use imports gain call edges in Rust repositories, so the output of codegraph callers, codegraph callees and codegraph impact changes for those repositories.
Before submitting
- I searched existing issues and this is not a duplicate
- I verified that the current behavior is not a deliberate decision in
openspec/specs/
🤖 Generated with Claude Code
https://claude.ai/code/session_0167Dcyr16pdkFTrCBgBTzoV
- Lenguaje dominante
- Go
- Estrellas
- 0
- Forks
- 0
- Merge medio
- 7 h 42 min
- PR fusionados (30 d)
- 111
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de seanb4t/codegraph-go
-
chore needs-triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
seanb4t/codegraph-go#380 ·
Los mantenedores suelen responder en 1 día
-
chore needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
seanb4t/codegraph-go#379 ·
Los mantenedores suelen responder en 1 día
-
area:query chore needs-triage spec-needed
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
seanb4t/codegraph-go#377 ·
Los mantenedores suelen responder en 1 día
-
chore needs-triage
Dificultad 1/5 1-3 horas Aptitud para principiantes 84/100
seanb4t/codegraph-go#362 ·
Los mantenedores suelen responder en 1 día
-
area:query bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
seanb4t/codegraph-go#355 ·
Los mantenedores suelen responder en 1 día
Todos los issues de seanb4t/codegraph-go
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día
-
automated documentation maintenance
Dificultad 1/5 1-3 horas Aptitud para principiantes 75/100
github/gh-aw-mcpg#16717 ·
Los mantenedores suelen responder en 1 día
-
Docs: Recording rules pages don't say what happens to a recorded metric when its rule is deletedAbiertointernal
Dificultad 1/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
jesseduffield/lazygit#6229 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
prometheus/prometheus#20482 ·
Los mantenedores suelen responder en 2 días