Solution:Step 1: Understand force unwrap assignmentForce unwrapping copies the value inside optional to a non-optional variable.Step 2: Effect of changing original optional laterChanging optionalString to nil does not affect forcedString which holds a separate value.Final Answer:No danger, forcedStr

[Solved] Given this code:var optionalString: String? = "Swift" var forcedString: String = optionalString!What is the danger if optionalString is later set to nil and forcedString is accessed? | Swift

Swift - Optionals

Given this code:

var optionalString: String? = "Swift"
var forcedString: String = optionalString!

What is the danger if optionalString is later set to nil and forcedString is accessed?

ARuntime crash when accessing forcedString

BCompiler error on assignment

CforcedString becomes nil automatically

DNo danger, forcedString is a non-optional copy

Step-by-Step Solution

Solution:

Step 1: Understand force unwrap assignment
Force unwrapping copies the value inside optional to a non-optional variable.
Step 2: Effect of changing original optional later
Changing optionalString to nil does not affect forcedString which holds a separate value.
Final Answer:
No danger, forcedString is a non-optional copy -> No danger, forcedString is a non-optional copy
Quick Check:
Force unwrap copies value, later nil optional safe [OK]

Quick Trick: Force unwrap copies value; later nil optional won't crash [OK]

Common Mistakes:

Thinking forcedString depends on optionalString after assignment
Expecting runtime crash on forcedString access
Confusing optional and non-optional variables

Master "Optionals" in Swift

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More Swift Quizzes

Given this code:

Step 1: Understand force unwrap assignment

Step 2: Effect of changing original optional later

Final Answer:

Quick Check:

Want More Practice?