<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Nov 26, 2017, at 9:21 PM, John McCall <<a href="mailto:rjmccall@apple.com" class="">rjmccall@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" class=""><div class=""><br class="Apple-interchange-newline">On Nov 22, 2017, at 1:08 PM, Douglas Gregor 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=""><div dir="auto" class=""><br class=""><br class=""><div class="">Sent from my iPhone</div><div class=""><br class="">On Nov 22, 2017, at 9:48 AM, Chris Lattner <<a href="mailto:clattner@nondot.org" class="">clattner@nondot.org</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class="">IMO this is obvious and you should put it in.<div class=""><br class=""></div><div class="">The process serves a purpose: to ensure the evolution of the language is going in the right place, both directionally in an details. It is obvious that we’re going to take this, and the details are clear, therefore doing an evolution cycle for this would just waste everyone’s time.</div></div></blockquote><div class=""><br class=""></div>I’ve been leaning this way as well. We can treat this small addition as an amendment to SE-0143 so the change is documented appropriately. </div></div></blockquote><div class=""><br class=""></div>Agreed. I think bringing it up here and letting it "pass by acclamation" is the appropriate process; doing a separate proposal would be a waste.</div></div></blockquote><br class=""></div><div>To close the loop here, the core team has agreed to this as an amendment to SE-0143, and the changed has been merged here:</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/apple/swift-evolution/pull/769" class="">https://github.com/apple/swift-evolution/pull/769</a></div><div><br class=""></div><div>and we’ve merged the change into the Swift standard library for Swift 4.1, here:</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/apple/swift/pull/13046" class="">https://github.com/apple/swift/pull/13046</a></div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div><br class=""></div></body></html>