<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Are these function names being based on the present participle of each verb, e.g. 'union' and 'intersect'? <div><br></div><div>The present participle of 'union' is technically speaking, 'unioning'. But it is not widely used. In fact, in both Pages and Word, 'unioning' is flagged as a misspelling of 'union'.<div><br></div><div>The present participle of 'intersect' is 'intersecting'; 'intersection' is a noun. </div><div><br></div><div>As currently presented, the use of 'union' and 'intersection' are a mixing of rarely used though correct present participle verb tense and a noun. I think it would be better to recognize that 'union' and 'intersection' are two universally used mathematical terms and to forego the suggested <span style="background-color: rgba(255, 255, 255, 0);">verb tense</span> gymnastics. </div><div><div><br><div><span class="Apple-style-span" style="-webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469);"><div>Jim</div><div><br></div><div><a href="mailto:jimhillhouse@me.com">jimhillhouse@me.com</a></div><div>512-484-9489</div><div><br></div><div>Sent from Jim's iPhone</div><div><br></div></span></div></div><div><br>On Feb 11, 2016, at 12:09 PM, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div>MHO: +1 on the intention of using less unwieldy names, but -1 on the specific solution. I fear that the current solution has some inexplicable inconsistencies and some Englishing which verges, again MHO, on Hungarianisms that others have mentioned are to be explicitly avoided.<br><br>For example, why is it intersection() but unioning()? Surely it should be either intersecting() and unioning() or intersection() and union()? Also, I understand that there's precedent elsewhere and that uniting() is not a good counterpart to union(), but unioning() is a pretty unsavory mangling of the noun. And then we have exclusiveOring(), which is just not English.<br><br><div class="gmail_quote"><div dir="ltr">On Thu, Feb 11, 2016 at 11:38 AM Dave Abrahams via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi All,<br>
<br>
The API guidelines working group took up the issue of the InPlace suffix<br>
yesterday, and decided that it was not to be used anywhere in the<br>
standard library. We are planning to apply the changes shown here<br>
<<a href="https://gist.github.com/dabrahams/d872556291a3cb797bd5" rel="noreferrer" target="_blank">https://gist.github.com/dabrahams/d872556291a3cb797bd5</a>> to the API of<br>
SetAlgebra (and consequently Set) to make it conform to the guidelines<br>
under development.<br>
<br>
Comments welcome as usual,<br>
<br>
--<br>
-Dave<br>
<br>
_______________________________________________<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" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></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">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></div></div></body></html>