> On 3 Aug 2017, at 08:00, Slava Pestov <[email protected]> wrote: > > >> On Aug 2, 2017, at 10:48 PM, David Hart <[email protected] >> <mailto:[email protected]>> wrote: >> >> Somewhat related: I have a similar problem in a project where I need two >> different Codable conformances for a type: one for coding/decoding from/to >> JSON, and another one for coding/decoding from/to a database row. The keys >> and formatting are not identical. The only solution around that for now is >> separate types, which can be sub-optimal from a performance point of view. > > Actually if the wrapper types are structs with a single field, their use > should not introduce any additional overhead at runtime.
I ❤️ Swift > Slava
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
