Swift's implicitly unwrapped optionals: they stared into the abyss of null pointer exceptions, and liked what they saw.
Conversation
Replying to
For the most part, they’re for bridging over unannotated Obj-C APIs. For pure Swift, their use is something of a red flag.
Replying to
Main use case in pure Swift is for things like doubly linked lists where you can’t initialize both ways at once…
1
2
1