• Use NSError based error & exception handling
• Use NS_ENUM enumerations (with standard format)
• nullable & nonnull attributes for parameters
• Swift interoperability (nullability, enums & error handling)
• Removed instance variables from public header
• Remove retain/release stubs
• Remove all deallocs

The current message name & source file/line information is added to the protocol error that wraps the transport error.

…or the top level object already.

…ontainer entries)

Allows implementing "description" by the application via category/extension

Was moved to TNSStreamTransport to make a general close method & keep streams private.  Instead we want the streams public and so the close method is moved back to its origin.

The new method uses SecTrustEvaluate on the stream's internal trust object.  Removes the deprecation warning given by previous implementation.

…ose method in TNSStream

All customization should be done via the NSURLSession & NSURLSession config.  This should be the preferred method so we enforce that by disallowing any customization of the request before usage.

All helper classes (e.g. _args & _result) are generated with the service name included. This fixes the issue with duplicate helper class names.

It could be as low as 6.0 but with 90% of the world on iOS 8. I don't think we need to worry about that.

Use positive error codes
HTTP error codes are more specific

• Generates all client and server code, uses Cocoa-ObjC based protocols and transports
• Compiles error free but completely untested
• Supports same options as original cocoa (aka ObjC) gerator including asynchronous protocols (both block and promise)

• Fixes problems with nested containers
• Uses wrapper containers for List, Set & Map; Swift currently disallows adding protocol conformance to generic types via extension (once it does the wrapper types can be discarded)
• Greatly simplifies read/write value code

Now generated in actual enum value

Generates proper Swift constants for all types

Validation is effectively always required to ensure Swift optional unwrapping doesn't throw errors

Swift was randomly handling default initializers for the enums incorrectly.  Some worked, some failed, no rhyme or reason. Putting the initalizer in the main enum declaration solves the issue

Provides uniform naming and stops confusion of Swift Set and Thrift Set

The application, protocol & transport exceptions are now reported in much the same conditions (and with same error code) as with other language bindings.  Java & CPP were used as examples of when to throw the correct exceptions.