Difference between Force Unwrapping Optionals and Implicitly Unwrapped Optionals

Question

I was very confused about forced unwrapping and implicit unwrapping at first. Now, the following understanding comes from my self-study:

There is no

Answer 1

An implicitly unwrapped optional is a normal optional behind the scenes, but can also be used like a non optional value, so yes you are correct.

But if you declare a value as implicitly unwrapped, it is equivalent to force unwrapping it at every use.

For Implicitly unwrapped Optionals there are 4 main reasons to do that.

1: A Constant That Cannot Be Defined During Initialization

2: Interacting with an Objective-C API

3: When Your App Cannot Recover From a Variable Being nil

4: NSObject Initializers