Skip to content
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

spec: clarification of "value receiver" vs "pointer receiver" (missing definition) #18828

Open
go101 opened this issue Jan 28, 2017 · 1 comment

Comments

@go101
Copy link

commented Jan 28, 2017

4 "value receiver" plus one "value-receiver".

Besides no definition for it, I feel it is better to be replaced with "non-pointer receiver", as pointers are also values.

@griesemer

This comment has been minimized.

Copy link
Contributor

commented Jan 30, 2017

@golang101 I agree that "non-pointer receiver" is technically more correct; though it feels a bit more "clunky" than "value receiver" (even though I agree that a pointer is technically also a value). I'm going to let this simmer for a bit. I'm not quite convinced that "non-pointer" is the right choice, or if there's a better term (or we just need to define "value receiver").

@griesemer griesemer changed the title spec: there are five "value receiver" occurrences in spec but no definition for it. spec: clarification of "value receiver" vs "pointer receiver" (missing definition) Jan 30, 2017
@griesemer griesemer added this to the Go1.9Maybe milestone Jan 30, 2017
@bradfitz bradfitz modified the milestones: Go1.10, Go1.9Maybe Jul 20, 2017
@rsc rsc modified the milestones: Go1.10, Go1.11 Dec 14, 2017
@ianlancetaylor ianlancetaylor modified the milestones: Go1.11, Unplanned Jun 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.