I would suggest xxxing and xxx naming like sorting and sort, e.g.:<div><br></div><div> y = x.unioning(z)</div><div> x.union(z)</div><div><br></div><div>The consistency of naming is more important to me than correct English. The reason for this preference is that it quickly becomes 2nd nature to know the names of variations and because the names begin with the same root and are therefore code completion friendly.</div><div><br>On Friday, 25 March 2016, Dave Abrahams via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Just an update:<br>
<br>
The naming guidelines working group went back into negotiation over<br>
the shape of SetAlgebra (and thus, Set and OptionSet) for<br>
Swift 3, and reached a new consensus. We intend to bring forward a<br>
proposal for the API shown here:<br>
<br>
<a href="http://dabrahams.github.io/swift-naming/SetAlgebra-Math.html" target="_blank">http://dabrahams.github.io/swift-naming/SetAlgebra-Math.html</a><br>
<br>
and to update the guidelines to suggest using the "form" prefix to<br>
create a verb phrase for a mutating method when the operation is<br>
fundamentally non-mutating and described by a noun.<br>
<br>
Regards,<br>
<br>
--<br>
Dave<br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')">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>
</blockquote></div><br><br>-- <br>-- Howard.<br>