Re:Understand Go pointers
by steveklabnik on Wednesday April 26, 2017 @10:53AM
(#14203455)
I've spent a lot of time on this, working on Rust's docs, and the way I see it is that "pointer" is the most generic concept, with "reference" being a more restricted form. So all references are pointers but not all pointers are references.
Words are hard.
So personally, I think of Go as having references, but not pointers (outside of unsafe).
Of course every language community uses those terms its own way, but that seems to me to be the most broadly useful way of looking at it.