Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> 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.



In fact it was “the Java way” for many years and “useless getters” was always a big complaint about Java.


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!


I do agree to a certain degree, but with getters/setters you could properly hide/set to read-only fields.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: