[swift-users] @noescape

[Nate Birkholz]

I saw elsewhere (In Chris Lattner's thread about ABI) that they are already
considering it as part of the base proposal, can anyone from the Swift team
confirm whether we need an official separate proposal?

On Tue, May 17, 2016 at 12:08 PM, Adriano Ferreira <adriano.ferreira at me.com>
wrote:

> Nate,
>
> Let me know if you’d like some help to write a draft/proposal. I’d be
> happy to help :P
>
> Best,
>
> — A
>
> On May 17, 2016, at 3:04 PM, Adriano Ferreira via swift-users <
> swift-users at swift.org> wrote:
>
> Here’s the related thread
> https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151214/003748.html
>
> Cheers,
>
> — A
>
> 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> wrote:
>
>>
>> On May 16, 2016, at 9:37 AM, Nate Birkholz via swift-users <
>> 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.
>>
>> —Jens
>>
>
>
>
> --
> Nate Birkholz
> _______________________________________________
> swift-users mailing list
> swift-users at swift.org
> https://lists.swift.org/mailman/listinfo/swift-users
>
>
> _______________________________________________
> swift-users mailing list
> swift-users at swift.org
> https://lists.swift.org/mailman/listinfo/swift-users
>
>
>


-- 
Nate Birkholz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-users/attachments/20160517/aa0a5a21/attachment.html>