golang/go

reflect: Value.Seq|Seq2 documentation and unexported value

Open

#74,377 创建于 2025年6月25日

在 GitHub 查看
 (12 评论) (0 反应) (0 负责人)Go (133,883 star) (19,008 fork)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
议题类型
documentation
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Go programmingreflect package basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
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.