2 ms·

> No immutable types (in Go) The typical answer is opaque types with only readonly methods exported. Not elegant, but it’s there. I guess it’s arguably not a “

by oefrha 7mo ago

> No immutable types (in Go) The typical answer is opaque types with only readonly methods exported. Not elegant, but it’s there. I guess it’s arguably not a “good way” to do it.

joeblubaugh 7mo ago
In fact it was “the Java way” for many years and “useless getters” was always a big complaint about Java.
- oefrha 7mo ago
  Hey it's better in Go. In Java it's getFoo(). In Go it's just Foo(). Saves three bytes, and three keystrokes if you program by hand and don't autocomplete!
- gf000 7mo ago
  I do agree to a certain degree, but with getters/setters you could properly hide/set to read-only fields.