[swift-evolution] [Rejected] SE-0097: Normalizing naming for "negative" attributes
clattner at apple.com
Tue Jun 7 22:39:53 CDT 2016
> On Jun 1, 2016, at 11:29 PM, Jacob Bandes-Storch <jtbandes at gmail.com> wrote:
> On Wed, Jun 1, 2016 at 10:25 PM, Chris Lattner <clattner at apple.com <mailto:clattner at apple.com>> wrote:
> On Jun 1, 2016, at 9:28 PM, Jacob Bandes-Storch <jtbandes at gmail.com <mailto:jtbandes at gmail.com>> wrote:
>> 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.
>> This part is what I proposed last year; still waiting on an update:
>> https://github.com/apple/swift-evolution/blob/master/proposals/0012-add-noescape-to-public-library-api.md <https://github.com/apple/swift-evolution/blob/master/proposals/0012-add-noescape-to-public-library-api.md>
> The problem with that proposal, and the reason it is sitting around in limbo is:
> 1) it is prescriptive of a process “Audit system C/Objective-C libraries...", not a proposal for a set of specific changes.
> 2) swift-evolution isn’t the right place to propose changes for Foundation or other APIs outside of the standard library.
> 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?
> Okay, but is there any other way the community can have input on the set of functions/methods that should be updated, and some visibility into whether/when this will happen? It was my impression that Philippe was making progress on this, but I hadn't heard any more for a while. (My concern would be APIs getting missed due to lack of community input.)
At this point it is hard to say. All I know is that the only process for this is to discuss it on the list (in which case many Apple folk will probably notice and make take it up on their own volition) or by filing a bug with bugreporter.apple.com <http://bugreporter.apple.com/> requesting it. Neither of these approaches give you the transparency you seek into when or if it will happen.
I understand that this isn’t what you want to hear, but it’s just the reality that Apple’s general framework design and evolution is not governed by the swift-evolution process.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution