feat: Go extractor records no read of a composite-literal element value

未关闭
#356 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
68/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
go
领域
tooling

调研方向

Start in internal/indexer/goextract/goextract.go: the composite_literal case of captureExprRead (~1184) delegates to captureCompositeElements (~1249) and captureElementWrites (~1277), which only record field writes. Add a read for each element value (bare identifier, selector, call, nested literal) across slice, struct, map-key and map-value positions, and fix the stale comment at 956-962. Check behavior with the p.go repro and internal/indexer/bindings_test.go, then run task golden:regen and task corpora:measure and update the hugo goldens, corpora/observations.json, docs/CORPUS-MEASUREMENT.md, matrix.go:101 and docs/LANGUAGE-CAPABILITY-MATRIX.md:126.

由索引模型根据 Issue 内容生成。

描述

area:indexer enhancement needs-triage
What exists today?

internal/indexer/goextract/goextract.go records no read for a value that a composite literal element holds.

How does it behave now?

Repro in a file p.go:

package p

type T struct{ F int }

func f(v, a, b int) {
	_ = T{F: v}
	_ = []int{a, b}
	_ = map[int]int{a: b}
}

f gets a write reference to F and an instantiates reference to T. f gets no read reference to v, a or b. The map key a gets no read either.

The cause is in the composite-literal path:

  • collectReferencesAndInstantiates sends a composite_literal to captureExprRead and stops (goextract.go:986).
  • The composite_literal case of captureExprRead (goextract.go:1184-1188) calls recordInstantiate and captureCompositeElements. It never reads an element value.
  • captureCompositeElements (goextract.go:1249-1272) records only an AccessWrite member reference for a keyed element.
  • captureElementWrites (goextract.go:1277-1299) acts only on literal_value, composite_literal and unary_expression. A bare identifier, selector or call records nothing.
  • captureExprRead has no literal_element case.

The block comment at goextract.go:956-962 says element values are read positions. The code does not do that, so the comment is stale.

The gap is recorded as a known limit in internal/indexer/capability/matrix.go:101 and docs/LANGUAGE-CAPABILITY-MATRIX.md:126. #342 left it open because recording the reads changes explore ranking and a hugo golden.

Effect: codegraph node and callers-style read queries miss these reads. The planned Accessed by ← line in #335 misses them too.

How should it behave?

A composite-literal element value records a read reference from the enclosing function. This covers bare identifiers, selectors, calls and nested literals, in slice elements, struct fields, map keys and map values. A keyed struct element still records its write to the field.

For the repro, f gets read references to v, a and b. It keeps the write to F and the instantiates reference to T.

The same change must fix the stale comment at goextract.go:956-962.

The fix changes these artifacts, and the PR must update each one:

  • Hugo goldens under testdata/golden/corpus/hugo/ (go-explore*.json, probably go-node*.json), checked by TestGoldensMatchLiveEngineOutput.
  • corpora/observations.json and docs/CORPUS-MEASUREMENT.md.
  • The matrix entries at matrix.go:101 and docs/LANGUAGE-CAPABILITY-MATRIX.md:126.

Whether TestExtract_Instantiates, TestExtract_InstantiatesUnnamedTypeNoRef or TestGoFieldWritesWithholdCalls (internal/indexer/bindings_test.go) needs changes is open until the fix runs.

Run task golden:regen and task corpora:measure in the same PR.

What kind of improvement?

Correctness in an edge case

Would this change existing behavior?

Yes. Each composite-literal element adds a read reference, so these outputs change:

  • codegraph node and callers-style read queries list more readers.
  • Explore ranking changes, which regenerates the hugo goldens.

The output shapes stay the same. Only the set of read entries changes.

Before submitting
  • I searched existing issues and this is not a duplicate
  • I checked that the current behavior is not a deliberate decision in openspec/specs/

🤖 Generated with Claude Code

主要语言
Go
星标
0
派生
0
平均合并
7 小时 42 分钟
30 天内合并 PR
111

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

seanb4t/codegraph-go 的其他 Issue

查看 seanb4t/codegraph-go 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。