<div dir="ltr">On Thu, Apr 13, 2017 at 7:46 PM, Guillaume Lessard <span dir="ltr"><<a href="mailto:glessard@tffenterprises.com" target="_blank">glessard@tffenterprises.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
> On Apr 13, 2017, at 18:18, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
> `compare(_:)` does not merit a term-of-art exception when the Swift name is clearly `compared(to:)`.<br>
<br>
</span>No; in full grammatical pedanticity it should be compared(with:).<br>
“compare to” is for dissimilar things.<br>
“compare with” is for similar things.<br>
(I’m not claiming that anyone cares, and I may have a traditional interpretation.)<br></blockquote><div><br></div><div>I have read the entirety of the OED entry on "compare," and I have found no evidence to support that. There are some usages that prefer "to" over "with," and some vice versa, but it is not by degree of similarity.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If the whole thing remains couched in terms of comparison, I prefer the function to be named compare(_:), because it’s such an everyday term. No one expects this action to possibly have a side effect.<br>
<br>
Cheers,<br>
Guillaume Lessard<br>
<br>
</blockquote></div><br></div></div>