<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 6, 2015, at 6:40 AM, 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=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I love that the team has released API Design Guidelines and find them very helpful. One piece of advice, however, seems to be at odds with current Standard Library practice.<div class=""><br class=""></div><div class="">Currently the methods sort() and sortInPlace() are the non-mutating and mutating versions of sorting a collection. Similarly, there are pairs of methods in Set named union() and unionInPlace(), intersect() and intersectInPlace() and so on.</div></div></div></blockquote><br class=""></div><div>Hi Daniel,</div><div><br class=""></div><div>This is a known issue, and it is because we want to keep Swift 2.2 reasonable source compatible with Swift 2. The changes to the standard library will land after Swift 2.2 branches for its release in the spring. </div><div><br class=""></div><div>If you’re interested in more details on this effort, check out this blog post:</div><div><a href="https://swift.org/blog/swift-3-api-design/" class="">https://swift.org/blog/swift-3-api-design/</a></div><div><br class=""></div><div>It includes a link to the diff-in-progress for the standard library.</div><div><br class=""></div><div>-Chris</div><br class=""></body></html>