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

Chris Lattner clattner at apple.com
Fri Dec 11 01:07:04 CST 2015

This LGTM as far as being a well thought out proposal, and I’d certainly like to see COpaquePointer go away. :-)

One thing to consider incorporating into your proposal, we’re trying to keep Swift 2.2 source compatible with Swift 2 (thought providing migration warnings where it makes sense).  Should your proposal wait for swift 3, or is there some piece that would be good to go into swift 2.2 to aid migration?


> On Dec 10, 2015, at 10:58 PM, Jacob Bandes-Storch <jtbandes at gmail.com> wrote:
> 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"?
> Jacob
> On Tue, Dec 8, 2015 at 9:52 PM, Chris Lattner <clattner at apple.com <mailto:clattner at apple.com>> wrote:
> On Dec 8, 2015, at 8:07 PM, Jacob Bandes-Storch via swift-evolution <swift-evolution at swift.org <mailto: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.
> -Chris

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

More information about the swift-evolution mailing list