[danusha2345]

Standalone off main (b9ca4b7), one commit, both extraction arms. The extractor defect noted in #1731.

What

extractMethod never set isExported, so every Go method was indexed as unexported whatever the case of its name — 148 of 148 on a 42-file tree, func (w *rotatingLogWriter) Close() included — while plain functions carried the flag. codegraph-kernel/src/go.rs mirrored the omission literally (// extractMethod passes no isExported).

A method that is a top-level declaration (methodsAreTopLevel — Go is the only such extractor) now receives the extractor's isExported exactly as a function does, and go.rs sets is_exported from the same name-case rule in extract_method. Class members in other languages keep the flag unset on purpose: their reachability is the class's, and the JS/TS isExported walks the parent chain, so applying it to methods would re-mark every member of an exported class and diverge the tsjs kernel walker.

Measured

Same Go/Kotlin/JS tree, kernel rebuilt from this checkout and confirmed loaded with CODEGRAPH_KERNEL_DEBUG=1:

Go methods	base	this
exported	0	41
unexported	148	107

Close / String → exported, close → not. Functions unchanged (135 / 175). The wasm arm (CODEGRAPH_KERNEL=0) gives the same flags.

Tests

extraction.test.ts: a four-symbol Go file (Close, flush, Open, helper) asserting the flag on both methods and both functions; passes on the wasm arm and with the kernel loaded. kernel-scaffold, kernel-deep-nesting, kernel-grammar-parity: 31 passed with the rebuilt kernel.

Relationship to #1732: that PR judges Go visibility by the name's case precisely because this flag was unusable; with this in, the flag and the case agree, and #1732's rule can later read the flag.

Note after the rebase onto 6421644. Two comments in src/resolution/name-matcher.ts (from #1745, in isVisibleAcrossFiles and its Go branch) say the extractor's isExported is unset for every Go method. With this PR the flag is set from the name's case, so those comments become stale; the code there stays correct, because it judges by the first letter, which gives the same answer. This PR does not touch that file.

🤖 Generated with Claude Code

[danusha2345]

Rebased onto current main (2f1a99d): head 38d2b25. Conflicts were only the CHANGELOG and the neighbouring #1729 tests in extraction.test.ts. Kernel rebuilt; the Go test passes on both arms. Once this lands, the by-name-case rule #1745 carries for Go can read the flag instead.

[danusha2345]

Rebased onto current main (b715eb6): head 18b4b30, one commit. CHANGELOG was the only conflict. Kernel rebuilt; the Go extraction tests pass on both arms (kernel and CODEGRAPH_KERNEL=0).

[colbymchenry]

Thanks @danusha2345! Go methods finally carry their exportedness, so the dead-code report no longer lists exported methods (harbor went from 167 listed Go symbols to 3).

We landed it in #2857, with you as the author, plus one fix. Once methods were flagged exported, a call through a package name like log.Errorf(...) could resolve to a same-named method declared beside the function (1,384 call sites on harbor). Go never reaches a method through the package name, so that lookup now skips methods, with a test for it. Thanks also for pointing out the stale comments; we updated those. Closing this in favor of #2857, which is now merged.