News for hackers. Stuff that matters.
Re:Typed nils in Go 2 by nerdponx on Friday August 11, 2017 @02:25AM (#14987084)
I'm all for the idea that relational fields should be NOT NULL

What if the data is actually missing? How else do you record that information?

Re:Typed nils in Go 2 by zupa-hu on Friday August 11, 2017 @02:30AM (#14987111)
You use the default empty value, and have an extra field for missingness. Than you have real type safety.
Re:Typed nils in Go 2 by TheDong on Friday August 11, 2017 @03:11AM (#14987300)
Real type safety is sum types. If I need to express something that is present or missing, I should use a Maybe monad.

Having an extra field for "missingness" is less safe because the type system won't enforce that it is either missing or set, you could have it set to a value but marked as missing which is still ambiguous.

Re:Typed nils in Go 2 by sorkin2 on Friday August 11, 2017 @06:21AM (#14988151)
That's a "cure" worse than the disease.
Re:Typed nils in Go 2 by taeric on Friday August 11, 2017 @10:18AM (#14989866)
If missing data is a valid value, pick a valid way to encode it. Null might work, but realize you could have to reason for the value. Actually missing, or just not collected it recorded.

I concede there may be no difference in those meanings.