Skip to content

Fix example of specifying value received method in -funcs #236

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rutsky
Copy link

@rutsky rutsky commented Jun 23, 2020

My experimentation shows that dir/pkg.Type.Method doesn't work, but (dir/pkg.Type).Method does.

Looking at https://golang.org/pkg/go/types/#Func.FullName implementation:
https://github.com/golang/go/blob/18bcc7c2854f900dfb631d7ef01a839021e24576/src/go/types/object.go#L465-L486

it seems to me that in both cases of pointer and value received the brackets are written.

CC: @alandonovan

My experimentation shows that `dir/pkg.Type.Method` doesn't work, but `(dir/pkg.Type).Method` does.

Looking at https://golang.org/pkg/go/types/#Func.FullName implementation:
https://github.com/golang/go/blob/18bcc7c2854f900dfb631d7ef01a839021e24576/src/go/types/object.go#L465-L486

it seems to me that in both cases of pointer and value received the brackets are written.
@gopherbot
Copy link
Contributor

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

Please visit https://go-review.googlesource.com/c/tools/+/239498 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

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://golang.org/doc/contribute.html#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.


Please don’t reply on this GitHub thread. Visit golang.org/cl/239498.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Michael Matloob:

Patch Set 1:

Could this be accompanied with a test?


Please don’t reply on this GitHub thread. Visit golang.org/cl/239498.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link
Contributor

Message from Go Bot:

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://golang.org/doc/contribute.html#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.


Please don’t reply on this GitHub thread. Visit golang.org/cl/239498.
After addressing review feedback, remember to publish your drafts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants