[swift-evolution] Immediately-called closures should be considered @noescape
Joe Groff
jgroff at apple.com
Tue Dec 15 17:20:14 CST 2015
> On Dec 15, 2015, at 3:16 PM, Brent Royal-Gordon via swift-evolution <swift-evolution at swift.org> wrote:
>
> Here’s a little annoyance I ran across just now:
>
> let sub: CKSubscription = {
> if let ID = self.ID {
> return CKSubscription(recordType: typeName, predicate: predicate, subscriptionID: ID, options: allMutations)
> }
> else {
> return CKSubscription(recordType: typeName, predicate: predicate, options: allMutations)
> }
> }()
>
> This closure obviously never leaves the enclosing function, but Swift doesn’t treat it as if it had been passed to a @noescape function, so I have to say “self.ID” instead of “ID” in the condition. That’s a bit irritating, and I’d like to see it improved.
Seems reasonable, especially because SILGen peepholes { }() so that it doesn't even allocate a closure to begin with.
-Joe
More information about the swift-evolution
mailing list