go/types, types2: document actual Interface.Method order by xThreeh · Pull Request #82083 · golang/go

xThreeh · 2026-10-08T18:36:29Z

The docs for Interface.Method and Interface.ExplicitMethod say the
methods are ordered by their unique Id. Since CL 461677 they are
sorted by Object.cmp instead: exported methods first, then by name
and, for non-exported methods with the same name, by package path.
The two orders differ when an interface has unexported methods from
more than one package. Describe the order that is implemented.

Fixes #81875

The docs for Interface.Method and Interface.ExplicitMethod say the methods are ordered by their unique Id. Since CL 461677 they are sorted by Object.cmp instead: exported methods first, then by name and, for non-exported methods with the same name, by package path. The two orders differ when an interface has unexported methods from more than one package. Describe the order that is implemented. Fixes golang#81875

gopherbot · 2026-10-08T18:49:19Z

This PR (HEAD: 9cefc6e) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/847325.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2026-10-08T19:34:05Z

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://go.dev/doc/contribute#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11 or adds a tag like "wait-release", it means that this CL will be
reviewed as part of the next development cycle. See https://go.dev/s/release
for more details.