The fact that safe language implementations have to think hard about how to handle null pointer exceptions safely should have been a warning sign that null pointers are a bad thing to have in a language. Sadly nearly always unheeded.
-
-
The only thing null has going for it is that it’s “simple”. Except it’s really not. It’s arguably a simple interface (though I disagree that the interface is simple), but it’s not a simple implementation. Isn’t Unix/worse-is-better supposed to be about implementation simplicity?
-
By the way, Swift goes to a ton of effort to eliminate redundant overflow checks at the SIL level, because it really does matter.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.