<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=""><div class="">FWIW, you can avoid the multiple-preposition issue it differently:</div><div class=""><br class=""></div><div class="">- isLessThanOrEqual(to:) => isNotGreaterThan(_:), isAtOrBelow(_:), etc.</div><div class=""><br class=""></div><div class="">…neither of which I can claim to really like, but such possibilities exist.</div><div class=""><br class=""></div><div class="">Offering in case there's a better phrasing along similar lines.</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Apr 20, 2016, at 3:08 PM, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="white-space:pre-wrap" class="">I'm saying something else. The preposition that goes with "less" is "than," while "to" goes only with "equal." By making "to" a parameter label you've got {less than or equal} to, which is inelegant because the label cannot be distributed to both parts--i.e. one cannot say "less than to or equal to."<br class=""><br class="">Put another way, I could just as well rewrite the method as `equalToOrLess(than:)`. Now, the parameter is labeled "than" instead of "to," yet the parameter serves the same purpose. Thus, I argue that the proposed method name may meet the letter of the Swift guidelines but is awkward.<br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Wed, Apr 20, 2016 at 14:44 Dave Abrahams via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="">
on Tue Apr 19 2016, Xiaodi Wu <<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>> wrote:<br class="">
<br class="">
> * What is your evaluation of the proposal?<br class="">
><br class="">
> +1 in intent. Specifics require further refinement. For example:<br class="">
><br class="">
> Internal inconsistencies in capitalization:<br class="">
> * `signalingNaN` but `isSignalingNan` and `isNan`<br class="">
><br class="">
> Parameter labels, or whatever they're called now, do not reflect newly<br class="">
> adopted Swift syntax in SE-0046:<br class="">
> * `static func maximum(x: Self, _ y: Self) -> Self` should be `static<br class="">
> func maximum(_ x: Self, _ y: Self) -> Self`, etc.<br class="">
><br class="">
> Infelicitous use of prepositions to conform superficially to new<br class="">
> naming guidelines:<br class="">
> * `isEqual(to:)` is fine, but for consistency there's<br class="">
> `isLessThanOrEqual(to:)`, which is not fine, because the preposition<br class="">
> "to" applies only to "equal" and not to "less than"<br class="">
<br class="">
That seems like a huge stretch to me. Are you claiming it's wrong to<br class="">
say “x is less than or equal to y,” or are you saying something else?<br class="">
<br class="">
--<br class="">
Dave<br class="">
<br class="">
_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
</blockquote></div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>