> On May 16, 2016, at 9:37 AM, Nate Birkholz via swift-users
> <swift-users@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
_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users
