<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 class="">Proposal link: <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0059-updated-set-apis.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0059-updated-set-apis.md</a></div><div class=""><br class=""></div><div class=""><br class=""></div>Hello Swift Community,<div class=""><br class=""></div><div class="">The review of SE-0059 "Update API Naming Guidelines and Rewrite Set APIs Accordingly” ran from March 31...April 5, 2016. The proposal is <b class="">accepted</b>. </div><div class=""><br class=""></div><div class="">There was much debate, both before and during the review, over the “InPlace” suffix/ “form” prefix, and at this point any answer will be objectionable to some. The core team has opted to accept the proposal as-is, keeping the “form” prefix to describe the mutating counterpart to an operation naturally described by a noun (e.g., “formUnion” for the mutating variant of “union”), for the reasons described in the proposal itself. Thanks all for the spirited discussion!</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div></body></html>