<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I started taking a look at the `NSJSONSerialization` work that needs to be done. I’ll send a pull-request for what I have once I get some more tests running. Anyone interested can see the first commit here: <a href="https://github.com/owensd/swift-corelibs-foundation/commit/29c840fa7089dd9370d8199591dbbeb733a0105f" class="">https://github.com/owensd/swift-corelibs-foundation/commit/29c840fa7089dd9370d8199591dbbeb733a0105f</a>.<div class=""><br class=""></div><div class="">That said, I’ve already seen some issues, I logged a couple here:</div><div class=""><br class=""></div><div class=""> - <a href="https://bugs.swift.org/browse/SR-71" class="">https://bugs.swift.org/browse/SR-71</a></div><div class=""> - <a href="https://bugs.swift.org/browse/SR-72" class="">https://bugs.swift.org/browse/SR-72</a></div><div class=""><br class=""></div><div class="">Another problem is how NSJSONSerialization works today. When things are not right (such as an invalid top-level JSON object), exceptions are raised. Obviously, this is not good. The function is marked with `throws` so I’ve started a new `ErrorType` implementation. I’ve started one here:</div><div class=""><br class=""></div><div class=""> public enum NSJSONSerializationError : ErrorType {<br class=""> case InvalidTopLevelType<br class=""> case InvalidKeyTypeForObject<br class=""> case InvalidValueType<br class=""> }</div><div class=""><br class=""></div><div class="">I’m not sure what the process really is here and how iterative you really want our pull requests. Any info would be helpful.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">-David</div><div class=""><br class=""></div></body></html>