News for hackers. Stuff that matters.
Re:Language Design Deal Breakers by protomyth on Saturday May 25, 2013 @11:25PM (#5769903)
> but it causes silent bugs, where you thought something was happening but it wasn't.

In Objective-C, it could be a silent bug or just intended behavior to send messages to a nil object. It is explained here: http://developer.apple.com/library/ios/#documentation/cocoa/...

Re:Language Design Deal Breakers by Strilanc on Sunday May 26, 2013 @01:34AM (#5770157)
Of course, the behavior may be intended. I've certainly taken advantage of nil doing nothing.

I've also accidentally had a nil where it wasn't expected, and lost time figuring out why particular effects weren't occurring. More time than I would have lost if the mistake had caused an immediate exception.

The same type of mistake is still possible (unexpected value), though the consequences are different, so I don't think it makes sense to say nil solves the null problem.