[swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer

Chris Lattner clattner at apple.com
Tue Dec 8 23:52:55 CST 2015

On Dec 8, 2015, at 8:07 PM, Jacob Bandes-Storch via swift-evolution <swift-evolution at swift.org> wrote:
> Proposed: https://github.com/apple/swift-evolution/pull/44 <https://github.com/apple/swift-evolution/pull/44>
A related topic that would be great to discuss for Swift 3: right now nullable C pointers import directly as UnsafePointer, and UnsafePointer are therefore nullable.  While it is true that they are unsafe :-), it would be more true to the Swift model to import them as optional unsafe pointers.

There are tradeoffs on both sides, just something to consider.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151208/18da55d4/attachment.html>

More information about the swift-evolution mailing list