[swift-evolution] [Pitch] make @noescape the default

Andrew Bennett cacoyi at gmail.com
Sat Dec 19 18:21:29 CST 2015

:+1: if it is more common, perhaps even if it isn't. Although I don't think
the standard library is the right place to look. I'm pretty sure if you did
the same check in Dispatch you'd find the opposite case.

I think production app code is probably a better place to look, although
I'm not sure of any good examples of open source swift 2 app code. It would
be nice for a lot of these proposals if there was a common reference list
of libraries and apps which are popular, mature, swift2 and open source so
we could gauge the impact.

On Sun, Dec 20, 2015 at 7:10 AM, Matthew Johnson via swift-evolution <
swift-evolution at swift.org> wrote:

> @noescape is safer because it does not require thinking about lifetime
> issues for captured objects.  My hunch was that @noescape (or @autoclosure
> with implies @noescape) is also more common.  I had a look through the
> standard library and this is definitely the case there.
> What does everyone think about making @noescape the default and
> introducing @escaping (or something similar) to annotate function arguments
> that do escape the call stack?
> Matthew
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151220/35fd78db/attachment.html>

More information about the swift-evolution mailing list