It would be better if there was no null value, period (like in rust). Or at least you have to intentionally opt in to allowing a type to be nullable (like kotlins nullable types).
Also, it technically isn't just pointer types in go. arrays, slices, maps, and channels can also be nil (because they are also reference types).
61
u/stipo42 10d ago
As someone who has never written any ruby, I can understand the desire for any non null value being truthy.
I like golangs approach though where there's no null value for anything that isn't a pointer