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 Swift side, or do we just write the entire implementation in Swift? From a
performance standpoint C is usually my go to, but if we use swift with only
structs and we really focus on minimizing use of functions that would be costly
/ do a lot of profiling and optimization we can get very close to equivalent
performance? At least to the level of the current objective c / c version? I'm
also not sure of potential performance penalties of calling C functions from
swift. Someone with more knowledge will have to weigh in on that one.
Thomas Leavy | Wickr Inc.
VP Mobile Applications & Architecture | Newark, NJ<x-apple-data-detectors://0/1>
On Dec 4, 2015, at 6:24 PM, swizzlr <m...@swizzlr.co<mailto:m...@swizzlr.co>>
wrote:
Re: Rules on adding dependencies
This e-mail message is intended only for the named recipient(s) above and is
covered by the Electronic Communications Privacy Act 18 U.S.C. Section
2510-2521. This e-mail is confidential and may contain information that is
privileged or exempt from disclosure under applicable law. If you have received
this message in error please immediately notify the sender by return e-mail and
delete this e-mail message from your computer, mobile devices and any cloud
storage backup systems as well as destroy any printed copy you might have made.
_______________________________________________
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
