adriano.ferreira at me.com
Tue May 17 14:04:35 CDT 2016
Here’s the related thread https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151214/003748.html <https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151214/003748.html>
> On May 16, 2016, at 12:43 PM, Nate Birkholz via swift-users <swift-users at swift.org> wrote:
> Well that was where I was going next, heh.
> On Mon, May 16, 2016 at 9:41 AM, Jens Alfke <jens at mooseyard.com <mailto:jens at mooseyard.com>> wrote:
>> On May 16, 2016, at 9:37 AM, Nate Birkholz via swift-users <swift-users at swift.org <mailto:swift-users at swift.org>> wrote:
>> I understand how @noescape works, and some of its benefits, I *think*, but if I am correct, it almost seems like it should be added automatically to my closure definitions until it becomes clear that the closure has to escape its context, much like I tend to declare variables as `let` until it becomes clear I need a `var`.
> IIRC, there is a current proposal to change the language in exactly that way — i.e. to have noescape be the default and use an attribute like “@escapes” to declare that a closure can be stored by the callee and called later.
> Nate Birkholz
> swift-users mailing list
> swift-users at swift.org <mailto:swift-users at swift.org>
> https://lists.swift.org/mailman/listinfo/swift-users <https://lists.swift.org/mailman/listinfo/swift-users>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-users