> On Aug 2, 2017, at 10:48 PM, David Hart <da...@hartbit.com> 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. Slava
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
