Cache bridge deserialization
struct User3: Codable, Defaults.Serializable {
let name: String
let age: String
}
extension Defaults.Keys {
static let user3 = Key<User3>("user3", default: .init(name: "Hello", age: "24"))
}
...
func test2() {
print(Defaults[.user3])
print(Defaults[.user3])
}
...The above code will call bridge.deserialize twice. If user3 is an array and there are many attributes of the User3 type, will it affect performance?
Would it be better to cache the data after Defaults[.user3] is executed once?
extension Defaults.Serializable {
....
static func toValue(_ anyObject: Any) -> Self? {
// Return directly if `anyObject` can cast to Value, since it means `Value` is a natively supported type.
if
isNativelySupportedType,
let anyObject = anyObject as? Self
{
return anyObject
} else if let value = bridge.deserialize(anyObject as? Serializable) {
return value as? Self
}
return nil
}
....
sindresorhus / Defaults
💾 Swifty and modern UserDefaults
2.1k
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too