But when Xcode generates subclasses, it doesn’t consider whether Core Data thinks the value is optional when generating the Swift file. It makes sure Core Data optionals become Swift optionals. From a Swift perspective, @NSManaged also tells the compiler that it doesn’t need to care whether the property has a value before initialization is complete, even if the property is not a Swift optional.