# \[Rejected\] SE-0097: Normalizing naming for "negative" attributes **URL:** \ **Category:** Announcements\ **Created:** [June 2, 2016, 4:02am UTC](https://forums.swift.org/t/rejected-se-0097-normalizing-naming-for-negative-attributes/2854 "2016-06-02T04:02:29Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![Chris\_Lattner](https://avatars.discourse-cdn.com/v4/letter/c/bc8723/32.png) [@Chris\_Lattner](https://forums.swift.org/u/Chris_Lattner)\ **Post date:** [June 2, 2016, 5:25am UTC](https://forums.swift.org/t/rejected-se-0097-normalizing-naming-for-negative-attributes/2854/9 "2016-06-02T05:25:12Z")
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? -Chris > **···** > > On Jun 1, 2016, at 9:28 PM, Jacob Bandes-Storch \ 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) --- _[View the full topic](https://forums.swift.org/t/rejected-se-0097-normalizing-naming-for-negative-attributes/2854)._