`guard` capture specifier for closure capture lists

[nonameplum (Łukasz)]

I like the idea and I described my thoughts some time ago in very similar way.

In a nutshell this syntax was proposed at the time:

{ [weak(guard) self] in ... }
{ [unowned(guard) self] in ... }

I would only suggest to even use shorter syntax to avoid writing weak and unowned and instead ? and !

{ [guard self?] in ... }
{ [guard self!] in ... }

Pitch: Syntactic sugar for circumventing closure capture lists

If you take a look at github repos and just to try find: guard let strongSelf = self else { return } guard let `self` = self else { return }` ... you will get bazillion results. The main problem is to understand when weak unowned should be used and even for experienced Swift users it is sometimes hard to grasp which one should be used as it strongly depends on the context. Thats why we have such situations were people add [weak self] regardless if is needed or not but it’s easier, and faster …