reflect: Value.Seq|Seq2 documentation and unexported value · golang/go#74377

(12 comments) (0 reactions) (0 assignees)Go (133,883 stars) (19,008 forks)batch import

DocumentationFixPendingSuggestedcompiler/runtimehelp wanted

説明

Go version

1.24

Output of `go env` in your module/workspace:

not relevant

What did you do?

Calling reflect.Value.Seq() panics if the value is unexported (CanInterface() returns false), but the documentation doesn't mention it.

What did you see happen?

It panics

What did you expect to see?

The documentation should explain that Seq() and Seq2() can be called if CanInterface() returns true, otherwise it panics. I guess we should add the same warning to Call() and CallSlice()

コントリビューターガイド

技術スタック: go
領域: documentation
Issue 種別: documentation
難度: 2
推定時間: under 1 hour
活動状況: active
明確さ: clear
前提条件: Go programmingreflect package basics
初心者向け度: 95
調査方針: Locate the documentation for Seq, Seq2, Call, and CallSlice methods in the reflect package's source code (likely in value.go). Add a note that these methods panic if CanInterface() returns false. Ensure consistency across all four methods. Also check if there are similar methods that might need the same warning. Review the discussion in the issue comments for any additional context. The fix involves adding a few lines to the method comments.

説明