No, Swift doesn't solve the null reference problem
-
There's been a lot of hype surrounding Apple's Swift language since its release. Some have claimed that, thanks to its support for optional types, it solves the null reference problem, Tony Hoare's "billion-dollar mistake". But that's not quite true. Let's see why.
Maybe Swift isn't that almighty, infallible incarnation of Objective-C everyone is heralding it as.
-
There's been a lot of hype surrounding Apple's Swift language since its release. Some have claimed that, thanks to its support for optional types, it solves the null reference problem, Tony Hoare's "billion-dollar mistake". But that's not quite true. Let's see why.
Maybe Swift isn't that almighty, infallible incarnation of Objective-C everyone is heralding it as.
By trying to solve the problem of negligence (and a NullReferenceException is typically caused by some kind of negligence somewhere), it will only cause more negligence.
-
By trying to solve the problem of negligence (and a NullReferenceException is typically caused by some kind of negligence somewhere), it will only cause more negligence.