fix(go): attribute calls inside top-level closures to the var, not the file (#693) (#744)

A function called only from an anonymous func_literal at package level — a
cobra `RunE: func(){…}` handler, a goroutine literal, a callback closure
stored in a `var` — had its call leak to the FILE node, because the Go
var-initializer walk ran with an empty scope. So `callers`/`impact` showed
the function with a file (or no meaningful) caller, unlike JS/TS where an
arrow-in-const becomes a named node whose calls attribute correctly.

Scope the Go top-level var/const initializer walk to the declared symbol, so
a call nested in any func_literal initializer (struct field, slice/map,
nested closure) attributes to the enclosing var. EXTRACTION_VERSION 3->4
(re-index to pick up the corrected attribution).

Validated on cli/cli (858 Go files): node/edge counts identical, file-level
dependents byte-identical (no regression), and 62 top-level-closure calls
correctly moved from file-attributed to var-attributed.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

This commit is contained in:

Colby Mchenry

2026-06-08 22:05:53 -04:00

committed by

GitHub

co-authored by

Claude Opus 4.8

parent 35b44e242c

commit 5b3f5e36db

4 changed files with 41 additions and 3 deletions

									
										src/extraction/extraction-version.ts
									
		+1
		-1
	
												View File
												
				@@ -21,4 +21,4 @@

				 * turns the re-index hint into noise — keep it honest (see CLAUDE.md, "Honesty

				 * in the product is load-bearing").

				 */

				export const EXTRACTION_VERSION = 3;

				export const EXTRACTION_VERSION = 4;