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>
Cheers, — A > On May 16, 2016, at 12:43 PM, Nate Birkholz via swift-users > <[email protected]> wrote: > > Well that was where I was going next, heh. > > On Mon, May 16, 2016 at 9:41 AM, Jens Alfke <[email protected] > <mailto:[email protected]>> wrote: > >> On May 16, 2016, at 9:37 AM, Nate Birkholz via swift-users >> <[email protected] <mailto:[email protected]>> 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 > [email protected] <mailto:[email protected]> > https://lists.swift.org/mailman/listinfo/swift-users > <https://lists.swift.org/mailman/listinfo/swift-users>
_______________________________________________ swift-users mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-users
