Fortunately, the compiler provides you a way to completely customize how Objective-C APIs end up in Swift. The compiler isn't that smart, so by default you'll end up with methods even if they are better defined as something else in Swift: M圜lass.sharedInstance() // would work better in Swift as `M圜lass.shared`!Īdditionally, the automatic API translation doesn't consider Swift-only features like default arguments and generics in methods, which are really good tools for developing APIs in Swift. However, what if you want that Objective-C API to become something completely different? One example of a common architectural difference between the languages is the usage of methods versus properties - most things in Objective-C are methods, while Swift will advise you to use computed properties for things that are computed but yet don't involve actually processing data. While I'm not a fan of how the naming can end up sometimes, there are attributes that you can use to finetune the final result, like NS_SWIFT_NAME(customName) to use a customized name or NS_SWIFT_NOTHROW to disable the error pointer -> throws conversion.

C to swift converter