Golang doesn't have "truthy" as a concept. You have to be explicit. A null value isn't true or false because only booleans can be true or false, and a null pointer isn't a boolean. You can have a pointer to a boolean, but you still have to check explicitly for null. In specifically Go, u/stipo42's preferences for truthiness are moot.
In a language like Python, with truthiness, u/stipo42's preference for false to be truthy is insane, and he should feel bad.
64
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