<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">This LGTM as far as being a well thought out proposal, and I’d certainly like to see COpaquePointer go away. :-)<div class=""><br class=""></div><div class="">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?</div><div class=""><br class=""></div><div class="">-Chris<br class=""><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 10, 2015, at 10:58 PM, Jacob Bandes-Storch <<a href="mailto:jtbandes@gmail.com" class="">jtbandes@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I haven't seen much feedback here. Are there any objections?<div class=""><br class=""></div><div class="">What's needed for a proposal to go from pull-request to "Awaiting Review"?<br class=""></div><div class=""><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature"><div dir="ltr" class=""><div class="">Jacob<br class=""></div></div></div></div>
<br class=""><div class="gmail_quote">On Tue, Dec 8, 2015 at 9:52 PM, Chris Lattner <span dir="ltr" class=""><<a href="mailto:clattner@apple.com" target="_blank" class="">clattner@apple.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">On Dec 8, 2015, at 8:07 PM, Jacob Bandes-Storch via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>> wrote:<div class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">Proposed: <a href="https://github.com/apple/swift-evolution/pull/44" target="_blank" class="">https://github.com/apple/swift-evolution/pull/44</a></div></div></blockquote><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">There are tradeoffs on both sides, just something to consider.</div><span class="HOEnZb"><font color="#888888" class=""><div class=""><br class=""></div><div class="">-Chris</div></font></span></div></div></blockquote></div><br class=""></div></div></div>
</div></blockquote></div><br class=""></div></div></body></html>