Re: [swift-corelibs-dev] Rules on adding dependencies

2015-12-05 Thread Tom Leavy
I would rather go right to the end game here and just work on coding up an implementation of JSON encoding / decoding and making it conform to the NSJSONSerialization spec. I can set up a repo for us to work on it. The main decision here, is do we code a small lib in C and then call it from the

Re: [swift-corelibs-dev] Rules on adding dependencies

2015-12-04 Thread Tom Leavy
par...@apple.com> wrote: Good idea, I filed a bug for that here. https://bugs.swift.org/browse/SR-59 - Tony On Dec 4, 2015, at 12:49 PM, Tom Leavy mailto:t...@wickr.com>> wrote: Hey Tony, That sounds like a good objective overall, thanks for clarifying. I think you guys should write that some

Re: [swift-corelibs-dev] Rules on adding dependencies

2015-12-04 Thread Tom Leavy
> rather than use one from another project. > > The one from Darwin is about 2k lines of Objective-C (actually, mostly C). > > - Tony > >> On Dec 4, 2015, at 11:21 AM, Tom Leavy wrote: >> >> I was wondering what the official position on introducing dep

[swift-corelibs-dev] Rules on adding dependencies

2015-12-04 Thread Tom Leavy
I was wondering what the official position on introducing dependencies currently is. I would love to contribute an implementation of NSJSONSerialization. I already have written a wrapper that uses yajl to take a CFDictionaryRef or CFArrayRef and encodes them into CFDataRef or CFStringRef JSON v