←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: 0.43s | 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. vbezhenar ◴[22 Aug 25 11:36 UTC] No.44983251[source]▶
Just use pointers everywhere? Who cares.
replies(1): >>44983749 #
2. softwaredoug ◴[22 Aug 25 12:31 UTC] No.44983749[source]▶
But just not a pointer to an interface.

Its annoying to need to think about whether I’m working with an interface type of concrete type.

And if use pointers everywhere, why not make it the default?