<div dir="ltr"><div>We could add @availability(*, deprecated=...) to the existing declarations but keep them around until Swift 3. I'm not sure whether this is preferable to simply waiting until Swift 3.</div><div><br></div><div>I'm also not sure how the migration stuff usually works, whether it'd be worth adding a migration step for this or just letting users see & fix the deprecation warnings themselves.</div><div><br></div>Earlier in this thread, Jordan said<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-size:12.8px">Swift does support overloading on return type, but the downside is you need to always provide context, which makes it harder to break things up into multiple statements. So we generally avoid it unless there's a compelling reason.</span><br></blockquote><div class="gmail_extra"><br></div><div class="gmail_extra">Either way, I'd be happy to prepare a patch for this, but I'm guessing I should wait until the proposal is accepted to do so.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div>Jacob<br></div></div></div></div>
<br><div class="gmail_quote">On Thu, Dec 10, 2015 at 11:07 PM, Chris Lattner <span dir="ltr"><<a href="mailto:clattner@apple.com" target="_blank">clattner@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">This LGTM as far as being a well thought out proposal, and I’d certainly like to see COpaquePointer go away. :-)<div><br></div><div>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><span class="HOEnZb"><font color="#888888"><div><br></div></font></span><div><span class="HOEnZb"><font color="#888888">-Chris</font></span><div><div class="h5"><br><div><br></div><div><br></div><div><br><div><blockquote type="cite"><div>On Dec 10, 2015, at 10:58 PM, Jacob Bandes-Storch <<a href="mailto:jtbandes@gmail.com" target="_blank">jtbandes@gmail.com</a>> wrote:</div><br><div><div dir="ltr">I haven't seen much feedback here. Are there any objections?<div><br></div><div>What's needed for a proposal to go from pull-request to "Awaiting Review"?<br></div><div><div class="gmail_extra"><br clear="all"><div><div><div dir="ltr"><div>Jacob<br></div></div></div></div>
<br><div class="gmail_quote">On Tue, Dec 8, 2015 at 9:52 PM, Chris Lattner <span dir="ltr"><<a href="mailto:clattner@apple.com" target="_blank">clattner@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">On Dec 8, 2015, at 8:07 PM, Jacob Bandes-Storch via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<div><blockquote type="cite"><div><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">Proposed: <a href="https://github.com/apple/swift-evolution/pull/44" target="_blank">https://github.com/apple/swift-evolution/pull/44</a></div></div></blockquote><div><br></div><div>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><br></div><div>There are tradeoffs on both sides, just something to consider.</div><span><font color="#888888"><div><br></div><div>-Chris</div></font></span></div></div></blockquote></div><br></div></div></div>
</div></blockquote></div><br></div></div></div></div></div></blockquote></div><br></div></div>