…o fix-swift-test* 'master' ofhttps://github.com/SwiftyJSON/SwiftyJSON:  Re-organize tests to satisfy SPM

…o fix-swift-test* 'master' ofhttps://github.com/SwiftyJSON/SwiftyJSON:  update Integration section of README to reflect latest version in SPM usage subsection  Fix duplicate comma typo  update readme  make casting nil to nsnull optional  represent strings with nil as if it was nsnull  Instead of checking for the Int8 type explicitly when setting 'object', cast the Int8 value to an Int and pass that into an NSNumber when setting 'int8' or 'int8Value'  Update version in pod spec  Add performance test  Attemp tofix#697  Fix 'AnyObject' in comment and README.md  The ‘isBool’ function on the NSNumber extension uses ‘trueObjCType’, which represents the type encoding for ‘true’ represented as an NSNumber, and ‘falseObjCType’, which represents the type encoding for ‘false’ represented as an NSNumber. Both type encodings are equal to ‘c’. However, an NSNumber that wraps around a value of type Int8 also has a type encoding of ‘c’. Therefore, a user who passes in a value of 0 or 1 (of type Int8) into JSON will expect to see the numbers 0 or 1 as the output because that was the intent. Unfortunately, that value will be wrapped into NSNumber and be considered a bool, so the user will see ‘true’ or ‘false’ instead.  Fix typo in README.md  Turn on render documentation mode.  Finish subscript part. Add descriptions.  Add getting a string using a path to the element.  Updating subscript section in playground  Added check for pre-escaped URLs to prevent double-escaping of % character# Conflicts:#Tests/SwiftyJSONTests/SequenceTypeTests.swift

…o fix-swift-test* 'master' ofhttps://github.com/SwiftyJSON/SwiftyJSON:  Fix travis_retry command not found  Update scripts  Fix all compilation warnings# Conflicts:#Tests/SwiftyJSONTests/NumberTests.swift#Tests/SwiftyJSONTests/RawTests.swift