<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 class="gmail_signature"><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 class="HOEnZb"><font color="#888888"><div><br></div><div>-Chris</div></font></span></div></div></blockquote></div><br></div></div></div>