Not clear on when to force unwrap to access a dictionary value (optionals)

Hi Chris,

That was how I roughly understood it and now since reading your explanation, fully understand it. However, the root of my confusion lies in that when I was experimenting in the playground and also by adding a println() statement for the value of title, the console returns Optional("Rise and Shine").

Yet when the app is run, the PlaylistDetailViewController displays the title as "Rise and Shine" without error.

So I'm still confused as to why the console shows the value for title as optional despite unwrapping during the downcast. And why if it's in fact an optional there is no error when pressing the button to display the title?

override func viewDidLoad() {
        super.viewDidLoad()
        println(playlist!.title)
        if playlist != nil {
            buttonPressLabel.text = playlist!.title
            println(playlist!.title)
            println(buttonPressLabel.text)
        }

    }

(All three of the above println() statements produce Optional("Rise and Shine") as output to the console)

Thanks for your help

Chris, does this mean that properties of type optionals are no longer optionals if they are set at initialisation?? That makes absolutely no sense to me - if it is declared optional, then it is always an optional even though you set it with an unwrapped value, no??? Also, I would argue that it makes no sense to declare a property optional, if you force unwrap it at initialisation, and never look back (check for nil everywhere else)...

I know there have been a few syntactic changes to swift since it was first introduced - but to be honest, I feel like the speaker is not 100% sure of how and when to use this feature of swift...

Btw.

buttonPressLabel.text = playlist?.title

is just as effective as

if playlist != nil {
  buttonPressLabel.text = playlist!.title
}

That's the beauty of it, and it just adds to the confusion that the speaker is unaware of this...

And Kevin, the reason your println statements all reflect an optional value, is that you are unwrapping the playlist, not the title... The title is still optional. The reason this works with the button label, though, is that the text property on a UILabel is also an optional - so it is quite allowed to set a labels text property to nil - and hence you don't have to unwrap it - like in my example above...