Hi Tony,
Sounds really excellent. Looking forward to it.
Please let me know if there's anything regarding proposal or implementation
that I can help with.
/morten
On Thu, Oct 19, 2017 at 5:09 PM Tony Parker
wrote:
> Hi Morten,
>
> I’ve actually been working on this same idea already and will hav
> On Oct 18, 2017, at 9:58 PM, Thorsten Seitz via swift-evolution
> wrote:
>
> In your earlier emails you wrote
>
> "To make it concrete, say you write a function that just wraps map:
> func firstNames(ofPeople people: Sequence) -> Sequence {
> return people.map { $0.firstName } }
> I want
Oh, this is weird... I replied to a different thread an hour ago. Somehow that
message hasn't posted yet, but this one from three days ago apparently got
reposted? Weird.
> On Oct 19, 2017, at 12:11 PM, David Sweeris via swift-evolution
> wrote:
>
>
> On Oct 16, 2017, at 10:42, BJ Homer via s
> On Oct 16, 2017, at 10:42, BJ Homer via swift-evolution
> wrote:
>
>>> On Oct 16, 2017, at 8:20 AM, Thorsten Seitz via swift-evolution
>>> wrote:
>>>
>>> Am 16.10.2017 um 07:19 schrieb Xiaodi Wu :
>>
>>> What useful generic algorithms would this protocol support that are not
>>> already
Yes, in general, I think Codable is a poor solution for json decoding just like
I never used NSCoding to convert JSON to and from objects. It feels clumsy.
I found it a much better solution to add a category to NSObject that had
-(NSData*)toJSONRepresentationWithMappings:(NSDictionary*)d
+()fro
On Thu, Oct 19, 2017 at 08:59 Mike Kluev wrote:
> On 19 October 2017 at 08:52, Xiaodi Wu wrote:
>
>> No, I'm talking about the implicit discardability proposed by Brent, such
>> as for all Optional<@discardable T>.
>>
>> He proposes that the @discardable syntax has a strong motivating
>> advanta
Hi Morten,
I’ve actually been working on this same idea already and will have something to
propose soon.
- Tony
> On Oct 19, 2017, at 2:03 AM, Morten Bek Ditlevsen via swift-evolution
> wrote:
>
> Hi all,
> At work we have just added Codable support for a whole bunch of model objects
> in o
On 19 October 2017 at 08:52, Xiaodi Wu wrote:
> No, I'm talking about the implicit discardability proposed by Brent, such
> as for all Optional<@discardable T>.
>
> He proposes that the @discardable syntax has a strong motivating advantage
> because it can be extended in a way to mark _types_ so
Hi all,
At work we have just added Codable support for a whole bunch of model
objects in our code base.
Many places we have added CodingKeys enumeration in order to convert the
camel cased property names to snake case for our JSON keys.
As an experiment I have tried adding a KeyCodingStrategy optio
