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.
-
-
By the way, Swift goes to a ton of effort to eliminate redundant overflow checks at the SIL level, because it really does matter.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I didn't appreciate the implementation difficulties until now. Still, we would not add null even if tomorrow's hardware makes null checks free. So in my view the case against null is not really about performance or implementation difficulty.
-
"We need to think hard about how to do X safely; that suggests X is bad" seems contrary to the spirit of Rust (and Swift and others). Haven't these languages been pioneers precisely through developers (such as yourself) thinking hard about how to do X safely?
- 2 more replies
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.