Crashing is better than ending up in an undefined state
Handling non-optional optionals in Swift
John Sundell
27312

While I agree with this sentiment as explicitly stated, I don’t think you should ever have an undefined state. Your UI should _always_ have a default state which is only altered if certain conditions are met.

In the case of a nil tableView, it seems you would have displayed some sort of empty set graphic until you have 1) items to display in a tableView & 2) a valid tableView for display.

Am I misunderstanding or leaving some special case out?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.