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

Jacob Bandes-Storch jtbandes at gmail.com
Fri Dec 11 00:58:00 CST 2015

I haven't seen much feedback here. Are there any objections?

What's needed for a proposal to go from pull-request to "Awaiting Review"?


On Tue, Dec 8, 2015 at 9:52 PM, Chris Lattner <clattner at apple.com> wrote:

> 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
> 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.
> -Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151210/bfc68d20/attachment.html>

More information about the swift-evolution mailing list