[swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals

Chris Lattner clattner at apple.com
Mon Feb 29 23:58:30 CST 2016

> On Feb 29, 2016, at 4:04 PM, Developer via swift-evolution <swift-evolution at swift.org> wrote:
> It is guarded in the same way that *(NULL) is guarded by an EXC_BAD_ACCESS.  It is all partiality in the end and beside the point I wished to make at the root of the discussion.  

Random ultra pedantic point, but dereferencing a null pointer in C (or an nil UnsafePointer in Swift) is actually undefined behavior, it is not guarded by a deterministic trap (as it is in Java).

Details here:


More information about the swift-evolution mailing list