<div dir="ltr"><div>You'd have to unwrap it, or use the ??/==/!= operators: <a href="https://gist.github.com/jtbandes/9d88cc83ceceb6c62f38">https://gist.github.com/jtbandes/9d88cc83ceceb6c62f38</a></div><div><br></div><div>I'd be okay with </<=/>/>= returning Bool?, as I suggested in an older email (which somehow didn't make it to gmane's archive, but it's quoted in <a href="http://thread.gmane.org/gmane.comp.lang.swift.evolution/10095">some other messages</a>). I think it would be more convenient in some cases than unwrapping the individual values before comparing them.</div><div><br></div><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Jacob<br></div></div></div></div>
<br><div class="gmail_quote">On Mon, Jul 11, 2016 at 8:08 PM, Saagar Jha <span dir="ltr"><<a href="mailto:saagarjha28@gmail.com" target="_blank">saagarjha28@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="font-family:SFUIText-Regular,"SF UI Text";font-size:12pt;color:rgb(0,0,0)"><div style="word-wrap:break-word">Correct me if I’m wrong, but wouldn’t you have to unwrap every comparison then?<div><div class="h5"><div><br><div><blockquote type="cite"><div>On Jul 11, 2016, at 20:02, David Sweeris via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div><div dir="auto"><div>Why not have them return a `Bool?`? If both arguments are non-nil, it can return the results of the comparison, otherwise it can return nil.<br><br>- Dave Sweeris</div><div><br>On Jul 7, 2016, at 16:37, Jacob Bandes-Storch via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>These operators cause some potential for confusion:</div><div><br></div><div><div> public func <<T : Comparable>(lhs: T?, rhs: T?) -> Bool</div><div> public func ><T : Comparable>(lhs: T?, rhs: T?) -> Bool<br></div><div> public func <=<T : Comparable>(lhs: T?, rhs: T?) -> Bool<br></div><div> public func >=<T : Comparable>(lhs: T?, rhs: T?) -> Bool</div><div><br></div><div>1. The meaning of T? < T? is not immediately obvious (Why is nil < .some(x) for any x? Personally, my intuition says that Optional should only provide a partial order, with .none not being ordered w.r.t. .some(x).)</div><div><br></div><div>2. Even if the meaning is understood, it can be surprising when the (T?, T?) -> Bool version is used instead of (T, T) -> Bool.</div><div><br></div><div>Prior discussion:</div><div>- <a href="http://thread.gmane.org/gmane.comp.lang.swift.devel/2089" target="_blank">http://thread.gmane.org/gmane.comp.lang.swift.devel/2089</a><br></div><div>- <a href="http://thread.gmane.org/gmane.comp.lang.swift.evolution/10095" target="_blank">http://thread.gmane.org/gmane.comp.lang.swift.evolution/10095</a></div></div><div><span style="font-size:12.8px">- <a>rdar://</a></span><span style="font-size:12.8px">16966712&</span><span style="font-size:12.8px">22833869</span></div><div><span style="font-size:12.8px">- Replies to <a href="https://twitter.com/jtbandes/status/646914031433871364" target="_blank">https://twitter.com/jtbandes/status/646914031433871364</a></span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">In the swift-dev thread from May, Chris said:</span></div><div><span style="font-size:12.8px"><br></span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">One of the ideas that Joe Pamer has been discussing is whether the implicit promotion from T to T? should be disabled when in an operator context. Doing so would fix problems like this, but making the code invalid.</span></blockquote><div style="font-size:12.8px"><br></div></blockquote><div><br></div><div>A change like this would be source-breaking, so if the core team has recommendations for how to handle these issues, now is probably the time to get it done.</div><br clear="all"><div><div data-smartmail="gmail_signature"><div dir="ltr"><div>Jacob<br></div></div></div></div>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></div>_______________________________________________<br>swift-evolution mailing list<br><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div></blockquote></div><br></div></div></div></div></div></div>
</blockquote></div><br></div></div>