You can send messages to `nil`, but the inverse isn't universally true. APIs like
reply [text stringByAppendingString:other];
You can send messages to null, sendings messages to a deallocated pointer is going to be a bad time.
replyIt’s nice not to crash, but unexpected null can still cause bugs in ObjC when the developer isn’t paying attention.
replyHaving done both ObjC with nonnull annotations, and Swift, I agree that it’d be hard to forgo the having first-class support for Optionals
deleted
reply