trending/codebase-memory-mcp
1
0
Fork 0
mirror of https://github.com/DeusData/codebase-memory-mcp.git synced 2026-10-29 07:13:44 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix(lsp): rank Go sole-implementer interface resolution at 0.95

Browse Source 
For a call through an interface with exactly one implementer (s.Speak()
where Speaker is implemented only by Dog), go_lsp emitted both
lsp_interface_resolve -> Dog.Speak at 0.90 and lsp_type_dispatch ->
Speaker.Speak at 0.95. The join keeps the highest-confidence resolution,
so type_dispatch (the interface-method node) always shadowed the concrete
sole-implementer resolution. A sole-implementer dispatch is unambiguous;
rank it 0.95 so the concrete Type.method wins for that call site.

go_py LSP strategy reproductions 15->16.

Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
This commit is contained in:
Martin Vogel
2026-06-28 00:59:38 +02:00
parent 6c1dfc92e9
commit c718d68390
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
internal/cbm/lsp/go_lsp.c
+6 -1
View File
@@ -1222,8 +1222,13 @@ static void resolve_calls_in_node(GoLSPContext* ctx, TSNode node) {
const CBMRegisteredFunc* concrete_method =
cbm_registry_lookup_method(ctx->registry, sole_impl_qn, field_name);
if (concrete_method) {
// Sole-implementer interface dispatch is an unambiguous
// resolution (exactly one concrete method); rank it at least
// as high as a direct type dispatch (0.95) so the concrete
// `Type.method` wins over the interface-method type_dispatch
// for the same call site.
emit_resolved_call(ctx, concrete_method->qualified_name,
"lsp_interface_resolve", 0.90f);
"lsp_interface_resolve", 0.95f);
goto recurse;
}
}