When writing the `handler` closure of a `UIAlertAction`, should the reference to `self` be strong (the default), `weak`, or `unowned`?

There have been posts relevant to this topic ([1](https://stackoverflow.com/questions/24320347/shall-we-always-use-unowned-self-inside-closure-in-swift), [2](https://stackoverflow.com/questions/25975073/swift-closures-capturing-self-as-weak), [3](https://stackoverflow.com/questions/24042949/block-retain-cycles-in-swift), [4](https://stackoverflow.com/questions/32936264/why-specify-unowned-self-in-blocks-where-you-depend-on-self-being-there)) but I honestly don&#39;t see how they help in this case.




Let&#39;s focus on this typical code:

    func tappedQuitButton() {
        let alert = UIAlertController(title: &quot;Confirm quit&quot;, message: nil, preferredStyle: .ActionSheet)

        let quitAction = UIAlertAction(title: &quot;Quit&quot;, style: .Default) { (action) in
            self.dismissViewControllerAnimated(true, completion: nil)
        }
        alert.addAction(quitAction)

        let cancelAction = UIAlertAction(title: &quot;Cancel&quot;, style: .Default) { (action) in
            self.dismissViewControllerAnimated(true, completion: nil)
        }
        alert.addAction(cancelAction)

        presentViewController(alert, animated: true, completion: nil)
    }

This is a function inside a `UIViewController` subclass, so `self` is the view controller presenting the alert.

The [documentation](https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swift_Programming_Language/AutomaticReferenceCounting.html) says: 

&gt;Use a weak reference to avoid reference cycles whenever it is possible for that reference to have “no value” at some point in its life. If the reference will always have a value, use an unowned reference instead. 

I may be blind, but I still don&#39;t see how this helps answering my question about `UIAlertAction`. 

In the above code, is it possible for `self` to be nil _at some point in its life_? Yes. So I should mark `self` as `weak`.

But then again, I can&#39;t think of a plausible scenario where `self` will be nil when the closure is called. So as far as that closure is concerned, `self` _will always have a value_. So I should mark `self` as `unowned`. 

So, again, how should `self` be captured in a UIAlertAction&#39;s handler?

All Uialertaction Solutions on Gang of Coders

Total of 1 Uialertaction Solutions

Should self be captured as strong in a UIAlertAction's handler?