Submitted as FB7734488, feel free to dupe.
jki
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
User for
From
Riga, Latvia
Post
Replies
Boosts
Views
Activity
Can confirm this issue on iOS 17.4 beta.
Similar question - if I wrap UserDefaults in the property wrapper (in my example to provide access to shared app group defaults).
@propertyWrapper
public struct HMASettingsDefault<Value> {
let key: String
let defaultValue: Value
var container: UserDefaults = UserDefaults.standard
public var wrappedValue: Value {
get {
return container.object(forKey: key) as? Value ?? defaultValue
}
set {
if let optionalValue = newValue as? AnyOptional, optionalValue.isNil {
container.removeObject(forKey: key)
}
else {
container.set(newValue, forKey: key)
}
}
}
}
Xcode will report
"is not concurrency-safe because it is non-isolated global shared mutable state" in all places where this wrapper is used e.g.
@HMASettingsDefault(key: "fixedAppTimezone", defaultValue: Calendar.current.timeZone.identifier, container: MyAppGroup.defaults)
static var userTimezoneId: String
What would be the best approach to use (promised) threadsafe objects in property wrappers in Swift6 strict concurrency world?