Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
spec: clarification of "value receiver" vs "pointer receiver" (missing definition) #18828
@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").