[swift-evolution] [Review] SE-0097: Normalizing naming for "negative" attributes
cheyo at masters3d.com
Sat May 28 14:21:02 CDT 2016
Are you talking about writing a proposal for @escaping or @once after it becomes feasible?
I haven't seen a proposal for making `noescape` the default. Do you think that is with in the swift 3 scope and goal of source braking changes?
This is where is I saw this first.
> On May 28, 2016, at 10:18 AM, Trent Nadeau <tanadeau at gmail.com> wrote:
> I agree with Jose. I especially like the idea of making `@noescape` the default with a new `@escaping` attribute. As I believed was mentioned in an earlier review, this would also make the proposed `@noescape(once)` just be `@once`. I'd be happy to write the proposal for that rename.
>> On Wed, May 25, 2016 at 12:43 PM, Jose Cheyo Jimenez via swift-evolution <swift-evolution at swift.org> wrote:
>> > * What is your evaluation of the proposal?
>> -1. noreturn is a term of art that is googable, renaming will make it obscure imo specially since it is not that common in iOS code.
>> If the core team were to keep `noreturn` then `nonscaping` will be weird,
>> but then if `noescape` became the default then (the non negative ;-) `escaping` would make sense.
>> > * Is the problem being addressed significant enough to warrant a change to Swift?
>> > * Does this proposal fit well with the feel and direction of Swift?
>> > * If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
>> > * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
>> read the thread.
>> swift-evolution mailing list
>> swift-evolution at swift.org
> Trent Nadeau
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution