This has been discussed many times in the past:
- Easy strongified weak `self` in closures
- Syntactic sugar for simplifying guards
- Pitch: Syntactic sugar for circumventing closure capture lists
- Proposal: weakStrong self in completion handler closures
- [Proposal Update 1] A simplified notation for avoiding the weak/strong dance with closure capture lists
IMHO it's not worth adding complexity to the language to save a few keystrokes in this scenario. The fact that you have to explicitly do this "dance" is for a good reason (clarity over terseness, which is important when dealing with weak/strong references).