<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=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On 19 Apr 2016, at 10:40, Brent Royal-Gordon 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=""><blockquote type="cite" class="">Totally agree with Brent, too. And I wouldn't rename flatten either.<br class=""></blockquote><br class="">A brief postscript on terms of art:<br class=""><br class="">I wrote my first Python this week. I was very glad that `map` was named `map`. I just had to glance at the docs to see whether it was a function or a method and which argument came first. It took less time and involved less doubt than learning their closure syntax did.</div></blockquote><br class=""></div><div>Are you suggesting that if it had been named “mapped” or “mapping” that you would have been unable to find it? Any decent search engine and/or auto-complete should get you to the correct function just as quickly, again, I don’t think anyone is suggesting that these functions be radically renamed, just that their tense be altered to match the new naming convention, which doesn’t change the root word from which they are derived.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class="">On 15 Apr 2016, at 12:49, Daniel Steinberg 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="">I agree with this and add that the 2.2 naming is unambiguous. There’s no doubt what is meant by sortInPlace().<br class=""></div></blockquote></div><br class=""><div class="">I’m normally in favour of more explicit meaning rather than less, but this where Swift’s type system and the <font face="Monaco" class="">@warn_unused_result</font> attribute come into play to eliminate the need for it:</div><div class=""><br class=""></div><div class=""><font face="Monaco" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>myCollection.sorted()<span class="Apple-tab-span" style="white-space:pre"> </span>// Warning, unused result</font></div><div class=""><font face="Monaco" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>let sorted = myCollectioned.sort()<span class="Apple-tab-span" style="white-space:pre"> </span>// Void return type</font></div><div class=""><br class=""></div><div class="">A more explicit term is only needed for functions where there is ambiguity in how they are used IMO, i.e- if a function is both mutating and has a return type. The fact that .sort() doesn’t return anything does a pretty good job of clarifying what it does.</div></body></html>