Skip to content

Conversation

@acehinnnqru
Copy link
Collaborator

@acehinnnqru acehinnnqru commented Oct 21, 2025

…not its receiver

What type of PR is this?

Check the PR title.

  • This PR title match the format: <type>(optional scope): <description>
  • The description of this PR title is user-oriented and clear enough for others to understand.
  • Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.

当是类的方法时,是否导出应该由方法的实际名字确定,而不是类的名字。

(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):
因为当这里是类的方法时,name 是 {struct name}.{method name},当然也可能是多层组合的 {struct name}.{struct name}.{method name},所以要根据 {method name} 的首字母来判断。

比如 struct a {} 有一个方法 func (*a) Do() 实际上这个 Do 方法是导出的;
struct A {} 有一个方法 func (*A) do() 实际上这个方法是非导出的。

(Optional) Which issue(s) this PR fixes:

(optional) The PR that updates user documentation:

@acehinnnqru acehinnnqru force-pushed the fix/go-exported-method branch from 88f1a11 to 5f3690a Compare October 21, 2025 11:57
@Duslia Duslia merged commit 3f4a4f8 into cloudwego:main Oct 21, 2025
2 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants