3 ms·

So many I wouldn't know where to start. Databases have had not-null constraints for years, but an accurate model often means having null values. A better impro

So many I wouldn't know where to start. Databases have had not-null constraints for years, but an accurate model often means having null values. A better improvement would be to handle null references better - Rails' whiny_nil support is great for example.

masklinn 16y ago
> So many I wouldn't know where to start. Databases have had not-null constraints for years, but an accurate model often means having null values. These nulls are a different issue than the initialization-originated nulls (that is in fact an other issue with null: they can mean both "I have nothing to put there" and "I forgot to put something there"). > A better improvement would be to handle null references better No. > Rails' whiny_nil support is great for example. whiny_nil exists because you can't do much more in a dynamically typed language, apart from making nil a message sink. Go is not a dynamically typed language, and statically typed language communities have found much better ways to handle most cases where you would use null references decades ago.