The Semantics of nil in Swift

This article explores the semantics of nil in Swift, comparing it with Objective-C. In Objective-C, nil is a pointer to 0x00000000 , but for non-pointer value types like NSInteger , there's no concept of 'no value'. Swift, as a strongly-typed language, introduces the concept of 'no value' from the beginning, using the nil keyword but with different semantics. For example, Int? can be nil or 0 , where 0 is a specific value, and nil is not.

The article then delves into how nil is represented in memory. Through code examples, it demonstrates that optional Int? types take up one more byte than regular Int types to indicate 'no value'. This can lead to memory waste in structs or classes with multiple optional fields due to memory alignment. However, the Swift compiler optimizes this by using different representations for various types:

Bool? : Uses 2 to represent 'no value', making it a three-state switch.

String? : Uses 0 to represent 'no value', as 0 is a valid value for strings.

Class? : Uses a null pointer to represent 'no value', similar to Objective-C.

Enum? : Uses an out-of-range value to represent 'no value', if possible.

The article concludes by advising developers to minimize the use of optional values in structs with multiple optional Int fields, using 0 instead if it satisfies the code logic.