[swift-evolution] Splat

Brent Royal-Gordon brent at architechies.com
Wed Feb 10 16:32:12 CST 2016

> However, I’d be reticent to start using ! for safe operations like dereferencing a (guaranteed memory safe) pointer.

A pointer dereference can cause a segfault. Even if you assume it's not pointing to unallocated memory, UnsafePointers can be nil, at least in Swift 2.

(The lvalue thing Joe Groff mentioned is also a concern, but adding inout return values would fix that in principle.)

Brent Royal-Gordon

More information about the swift-evolution mailing list