2 ms·
> I mostly avoid getters/setters in Go code, unless I have a lot of functions all related to the same thing similarly named. It's the return type that denotes t
by robertlagrant 4y ago
> I mostly avoid getters/setters in Go code, unless I have a lot of functions all related to the same thing similarly named. It's the return type that denotes the return. It's already in the function signature.
But I thought Golang doesn't have function overloading, so you also have to name the function appropriately for its use?
- throwaway2203 4y agoYupppp. But you can't let function names get too long or everyone will laugh at you for being a Java dev writing Go. Like I said, absurd.