<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="">On Jun 1, 2016, at 9:28 PM, Jacob Bandes-Storch <<a href="mailto:jtbandes@gmail.com" class="">jtbandes@gmail.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
On imported Objective-C API, the core team did a quick study of the Cocoa APIs and found that most closure/block parameters are escaping in practice. As such, the core team feels that it isn’t overly burdensome to ask that imported Objective-C APIs annotate their semantically noescape block parameters with the clang __attribute__((noescape)) attribute.<br class=""></blockquote><div class=""><br class=""></div><div class="">This part is what I proposed last year; still waiting on an update:</div><div class=""><br class=""></div><div class=""><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0012-add-noescape-to-public-library-api.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0012-add-noescape-to-public-library-api.md</a></div><div class=""> </div></div></div></div></div></blockquote><br class=""></div><div>The problem with that proposal, and the reason it is sitting around in limbo is:</div><br class=""><div class="">1) it is prescriptive of a process “Audit system C/Objective-C libraries...", not a proposal for a set of specific changes.</div><div class=""><br class=""></div><div class="">2) swift-evolution isn’t the right place to propose changes for Foundation or other APIs outside of the standard library. </div><div class=""><br class=""></div><div class="">It has been stuck in a crack for a long time, and has no hope of getting unstuck. I think that at this point the right thing is to close it. Is that ok with you?</div><div class=""><br class=""></div><div class="">-Chris</div></body></html>