←back to thread

Go is still not good

(blog.habets.se)
644 points ustad | 2 comments | 22 Aug 25 09:25 UTC | HN request time: 0s | source
Show context
softwaredoug ◴[22 Aug 25 11:31 UTC] No.44983216[source]▶
I like Go, but my main annoyance is deciding when to use a pointer or not use a pointer as variable/receiver/argument. And if its an interface variable, it has a pointer to the concrete instance in the interface 'struct'. Some things are canonically passed as pointers like contexts.

It just feels sloppy and I'm worried I'm going to make a mistake.

replies(7): >>44983251 #>>44983254 #>>44983637 #>>44985983 #>>44986255 #>>44986985 #>>45002523 #
1. spicyusername ◴[22 Aug 25 12:21 UTC] No.44983637[source]▶
...do you want a copy or the original object?
replies(1): >>44983963 #
2. tgv ◴[22 Aug 25 12:49 UTC] No.44983963[source]▶
Yup, that's it. If you're going to modify a field in the receiver, or want to pass a field by reference, you're going to need a pointer. Otherwise, a value will do, unless ... that weird interface thing makes you. I guess that's the problem?