Back

@manlycoffee Interesting. Not to try to correct but Go does not have nullabe/nillable values either, it has pointers that are used for both passing by reference AND making the variable/field "nullable" which IMO leads to problems, where one mixes up whether that's a pass-by-reference or a nullable field. Edit: actually my view is not strong on nullable fields, maybe the problems they solve are better solved in other ways. Probably so...

@varfrog closest that I came to solving this problem is to wrap pointer types into a custom container struct purely to hold a value or null.

Eliminates a lot of nil dereferencing programmer mistakes, but doesn't eliminate them completely.