Swift is a general-purpose, multi-paradigm, compiled programming language developed by Apple Inc. and the open-source community.
First released in 2014, Swift was developed as a replacement for Apple's earlier programming language Objective-C, as Objective-C had been largely unchanged since the early 1980s and lacked modern language features.
Swift works with Apple's Cocoa and Cocoa Touch frameworks, and a key aspect of Swift's design was the ability to interoperate with the huge body of existing Objective-C code developed for Apple products over the previous decades.
It is built with the open source LLVM compiler framework and has been included in Xcode since version 6, released in 2014.
On Apple platforms, it uses the Objective-C runtime library, which allows C, Objective-C, C++ and Swift code to run within one program.
Apple intended Swift to support many core concepts associated with Objective-C, notably dynamic dispatch, widespread late binding, extensible programming and similar features, but in a "safer" way, making it easier to catch software bugs; Swift has features addressing some common programming errors like null pointer dereferencing and provides syntactic sugar to help avoid the pyramid of doom.
Swift supports the concept of protocol extensibility, an extensibility system that can be applied to types, structs and classes, which Apple promotes as a real change in programming paradigms they term "protocol-oriented programming" (similar to traits).
Swift was introduced at Apple's 2014 Worldwide Developers Conference (WWDC).
It underwent an upgrade to version 1.2 during 2014 and a major upgrade to Swift 2 at WWDC 2015.
Initially a proprietary language, version 2.2 was made open-source software under the Apache License 2.0 on December 3, 2015, for Apple's platforms and Linux.
Through version 3.0 the syntax of Swift went through significant evolution, with the core team making source stability a focus in later versions.
In the first quarter of 2018 Swift surpassed Objective-C in measured popularity.
Swift 4.0, released in 2017, introduced several changes to some built-in classes and structures.
Code written with previous versions of Swift can be updated using the migration functionality built into Xcode.
Swift 5, released in March 2019, introduced a stable binary interface on Apple platforms, allowing the Swift runtime to be incorporated into Apple operating systems.
It is source compatible with Swift 4.
Swift 5.1 was officially released in September 2019.
Swift 5.1 builds on the previous version of Swift 5 by extending the stable features of the language to compile-time with the introduction of module stability.
The introduction of module stability makes it possible to create and share binary frameworks that will work with future releases of Swift.
Swift 5.5, officially announced by Apple at the 2021 WWDC, significantly expands language support for concurrency and asynchronous code, notably introducing a unique version of the actor model.
History
Development of Swift started in July 2010 by Chris Lattner, with the eventual collaboration of many other programmers at Apple.
Swift took language ideas "from Objective-C, Rust, Haskell, Ruby, Python, C#, CLU, and far too many others to list".
On June 2, 2014, the Apple Worldwide Developers Conference (WWDC) application became the first publicly released app written with Swift.
A beta version of the programming language was released to registered Apple developers at the conference, but the company did not promise that the final version of Swift would be source code compatible with the test version.
Apple planned to make source code converters available if needed for the full release.Platforms State of the Union, Session 102, Apple Worldwide Developers Conference, June 2, 2014
The Swift Programming Language, a free 500-page manual, was also released at WWDC, and is available on the Apple Books Store and the official website.
Swift reached the 1.0 milestone on September 9, 2014, with the Gold Master of Xcode 6.0 for iOS.
Swift 1.1 was released on October 22, 2014, alongside the launch of Xcode 6.1.
Swift 1.2 was released on April 8, 2015, along with Xcode 6.3.
Swift 2.0 was announced at WWDC 2015, and was made available for publishing apps in the App Store in September 21, 2015.
Swift 3.0 was released on September 13, 2016.
Swift 4.0 was released on September 19, 2017.
Swift 4.1 was released on March 29, 2018.
Swift won first place for Most Loved Programming Language in the Stack Overflow Developer Survey 2015 and second place in 2016.
On December 3, 2015, the Swift language, supporting libraries, debugger, and package manager were open-sourced under the Apache 2.0 license with a Runtime Library Exception, and Swift.org was created to host the project.
The source code is hosted on GitHub, where it is easy for anyone to get the code, build it themselves, and even create pull requests to contribute code back to the project.
In December 2015, IBM announced its Swift Sandbox website, which allows developers to write Swift code in one pane and display output in another.
The Swift Sandbox was deprecated in January 2018.
During the WWDC 2016, Apple announced an iPad exclusive app, named Swift Playgrounds, intended to teach people how to code in Swift.
The app is presented in a 3D video game-like interface which provides feedback when lines of code are placed in a certain order and executed.
In January 2017, Chris Lattner announced his departure from Apple for a new position with Tesla Motors, with the Swift project lead role going to team veteran Ted Kremenek.
During WWDC 2019, Apple announced SwiftUI with Xcode 11, which provides a framework for declarative UI structure design across all Apple platforms.
Official downloads for the Ubuntu distribution of Linux have been available since Swift 2.2, with more distros added since Swift 5.2.4, CentOS and Amazon Linux.
There is an unofficial SDK and native toolchain package for Android too.
Platforms
The platforms Swift supports are Apple's operating systems (Darwin, iOS, iPadOS, macOS, tvOS, watchOS), Linux, Windows, and Android.
Version history
Features
Swift is an alternative to the Objective-C language that employs modern programming-language theory concepts and strives to present a simpler syntax.
During its introduction, it was described simply as "Objective-C without the baggage of C".
By default, Swift does not expose pointers and other unsafe accessors, in contrast to Objective-C, which uses pointers pervasively to refer to object instances.
Also, Objective-C's use of a Smalltalk-like syntax for making method calls has been replaced with a dot-notation style and namespace system more familiar to programmers from other common object-oriented (OO) languages like Java or C#.
Swift introduces true named parameters and retains key Objective-C concepts, including protocols, closures and categories, often replacing former syntax with cleaner versions and allowing these concepts to be applied to other language structures, like enumerated types (enums).
Closure support
Swift supports closures (known as lambdas in other languages).
Closures are self-contained blocks of functionality that can be passed around and used in your code.
Closures can be thought of as an unnamed function.
Here is an example:
// Closure type, defined by its input and output values, can be specified outside the closure: let closure1: (Int, Int) -> Int = { arg1, arg2 in     return arg1 + arg2 }
// …or inside it: let closure2 = { (arg1: Int, arg2: Int) -> Int in     return arg1 + arg2 }
// In most cases, closure’s return type can be inferred automatically by the compiler.
// However, this functionality may not work for too complex expressions.
let closure3 = { arg1: Int, arg2: Int in     return arg1 + arg2 }
Swift has a trailing closure syntax like this: // This function takes a closure which receives no input parameters and returns an integer, // evaluates it, and uses the closure’s return value (an Int) as the function’s return value.
func foo(closure bar: () -> Int) -> Int {     return bar() }
// Without trailing closure syntax: foo(closure: { return 1 })
// With trailing closure syntax: foo { return 1 }
Starting from version 5.3, Swift supports multiple trailing closures:
// This function passes the return of the first closure as the parameter of the second, // and returns the second closure’s result: func foo(bar: () -> Int, baz: (Int) -> Int) -> Int {     return baz(bar()) }
// With no trailing closures: foo(bar: { return 1 }, baz: { x in return x + 1 })
// With 1 trailing closure: a(bar: { return 1 }) { x in return x + 1 })
// With 2 trailing closures (note that only the first closure’s argument name is omitted): a { return 1 } baz: { x in return x + 1 }
Here are the criteria for the trailing closure syntax:
If the last arguments of a function are closures you can use the trailing closure syntax.
The parameter name of the first trailing closure must be omitted.
The parameter names of the remaining trailing closures must not be omitted.
If all the arguments given to a function are trailing closures, you may omit the parentheses after the function's name.
Calls to a function with trailing closures must be parenthesized if used in a guard statement.
String support
Under the Cocoa and Cocoa Touch environments, many common classes were part of the Foundation Kit library.
This included the NSString string library (using Unicode, UTF-8 in Swift 5, changed from UTF-16), the NSArray and NSDictionary collection classes, and others.
Objective-C provided various bits of syntactic sugar to allow some of these objects to be created on-the-fly within the language, but once created, the objects were manipulated with object calls.
For instance, in Objective-C concatenating two NSStrings required method calls similar to this:
NSString *str = @"hello,"; str = [str stringByAppendingString:@" world"]; In Swift, many of these basic types have been promoted to the language's core, and can be manipulated directly.
For instance, strings are invisibly bridged to NSString (when Foundation is imported) and can now be concatenated with the + operator, allowing greatly simplified syntax; the prior example becoming:
var str = "hello," str += " world" Access control
Swift supports five access control levels for symbols: , , , , and .
Unlike many object-oriented languages, these access controls ignore inheritance hierarchies:  indicates that a symbol is accessible only in the immediate scope,  indicates it is accessible only from within the file,  indicates it is accessible within the containing module,  indicates it is accessible from any module, and  (only for classes and their methods) indicates that the class may be subclassed outside of the module.
Optionals and chaining
An important new feature in Swift is option types, which allow references or values to operate in a manner similar to the common pattern in C, where a pointer may refer to a value or may be null.
This implies that non-optional types cannot result in a null-pointer error; the compiler can ensure this is not possible.
Optional types are created with the Optional mechanism—to make an Integer that is nullable, one would use a declaration similar to var optionalInteger: Optional<Int>.
As in C#,"Nullable Types", C# Programming Guide, Microsoft.
Swift also includes syntactic sugar for this, allowing one to indicate a variable is optional by placing a question mark after the type name, var optionalInteger: Int?.
Variables or constants that are marked optional either have a value of the underlying type or are nil.
Optional types wrap the base type, resulting in a different instance.
String and String?
are fundamentally different types, the latter has more in common with Int?
than String.
To access the value inside, assuming it is not nil, it must be unwrapped to expose the instance inside.
This is performed with the !
operator:
let myValue = anOptionalInstance!.someMethod()
In this case, the !
operator unwraps anOptionalInstance to expose the instance inside, allowing the method call to be made on it.
If anOptionalInstance is nil, a null-pointer error occurs.
This can be annoying in practice, so Swift also includes the concept of optional chaining to test whether the instance is nil and then unwrap it if it is non-null:
let myValue = anOptionalInstance?.someMethod()
In this case the runtime calls someMethod only if anOptionalInstance is not nil, suppressing the error.
Normally this requires the programmer to test whether myValue is nil before proceeding.
The origin of the term chaining comes from the more common case where several method calls/getters are chained together.
For instance:
let aTenant = aBuilding.tenantList[5] let theirLease = aTenant.leaseDetails let leaseStart = theirLease?.startDate
can be reduced to:
let leaseStart = aBuilding.tenantList[5].leaseDetails?.startDate
The ?
syntax circumvents the pyramid of doom.
Swift 2 introduced the new keyword guard for cases in which code should stop executing if some condition is unmet:
guard let leaseStart = aBuilding.TenantList[5]?.leaseDetails?.startDate else {     //handle the error case where anything in the chain is nil     //else scope must exit the current method or loop } //continue, knowing that leaseStart is not nil
Using guard has three benefits.
While the syntax can act as an if statement, its primary benefit is inferring non-nullability.
Where an if statement requires a case, guard assumes the case based on the condition provided.
Also, since guard contains no scope, with exception of the else closure, leaseStart is presented as an unwrapped optional to the guard's super-scope.
Lastly, if the guard statement's test fails, Swift requires the else to exit the current method or loop, ensuring leaseStart never is accessed when nil.
This is performed with the keywords return, continue, break, or throw, or by calling a function returning a Never (e.g. fatalError()).
Objective-C was weakly typed and allowed any method to be called on any object at any time.
If the method call failed, there was a default handler in the runtime that returned nil.
That meant that no unwrapping or testing was needed, the equivalent statement in Objective-C:
leaseStart = [[[aBuilding tenantList:5] leaseDetails] startDate]
Would return nil, and this could be tested.
However, this also demanded that all method calls be dynamic, which introduces significant overhead.
Swift's use of optionals provides a similar mechanism for testing and dealing with nils, but does so in a way that allows the compiler to use static dispatch because the unwrapping action is called on a defined instance (the wrapper), versus occurring in the runtime dispatch system.
Value types
In many object-oriented languages, objects are represented internally in two parts.
The object is stored as a block of data placed on the heap, while the name (or "handle") to that object is represented by a pointer.
Objects are passed between methods by copying the value of the pointer, allowing the same underlying data on the heap to be accessed by anyone with a copy.
In contrast, basic types like integers and floating-point values are represented directly; the handle contains the data, not a pointer to it, and that data is passed directly to methods by copying.
These styles of access are termed pass-by-reference in the case of objects, and pass-by-value for basic types.
Both concepts have their advantages and disadvantages.
Objects are useful when the data is large, like the description of a window or the contents of a document.
In these cases, access to that data is provided by copying a 32- or 64-bit value, versus copying an entire data structure.
However, smaller values like integers are the same size as pointers (typically both are one word), so there is no advantage to passing a pointer, versus passing the value.
Also, pass-by-reference inherently requires a dereferencing operation, which can produce noticeable overhead in some operations, typically those used with these basic value types, like mathematics.
Similarly to C# and in contrast to most other OO languages, Swift offers built-in support for objects using either pass-by-reference or pass-by-value semantics, the former using the class declaration and the latter using struct.
Structs in Swift have almost all the same features as classes: methods, implementing protocols and using the extension mechanisms.
For this reason, Apple terms all data generically as instances, versus objects or values.
Structs do not support inheritance, however.
The programmer is free to choose which semantics are more appropriate for each data structure in the application.
Larger structures like windows would be defined as classes, allowing them to be passed around as pointers.
Smaller structures, like a 2D point, can be defined as structs, which will be pass-by-value and allow direct access to their internal data with no dereference.
The performance improvement inherent to the pass-by-value concept is such that Swift uses these types for almost all common data types, including Int and Double, and types normally represented by objects, like String and Array.
Using value types can result in significant performance improvements in user applications as well.
To ensure that even the largest structs do not cause a performance penalty when they are handed off, Swift uses copy on write so that the objects are copied only if and when the program attempts to change a value in them.
This means that the various accessors have what is in effect a pointer to the same data storage.
So while the data is physically stored as one instance in memory, at the level of the application, these values are separate and physical separation is enforced by copy on write only if needed.
Protocol-oriented programming
A key feature of Objective-C is its support for categories, methods that can be added to extend classes at runtime.
Categories allow extending classes in-place to add new functions with no need to subclass or even have access to the original source code.
An example might be to add spell checker support to the base NSString class, which means all instances of NSString in the application gain spell checking.
The system is also widely used as an organizational technique, allowing related code to be gathered into library-like extensions.
Swift continues to support this concept, although they are now termed extensions, and declared with the keyword extension.
Unlike Objective-C, Swift can also add new properties accessors, types, and enums to extant instances .
Another key feature of Objective-C is its use of protocols, known in most modern languages as interfaces.
Protocols promise that a particular class implements a set of methods, meaning that other objects in the system can call those methods on any object supporting that protocol.
This is often used in modern OO languages as a substitute for multiple inheritance, although the feature sets are not entirely similar.
A common example of a protocol in Cocoa is the NSCopying protocol, which defines one method, copyWithZone, that implements deep copying on objects.
In Objective-C, and most other languages implementing the protocol concept, it is up to the programmer to ensure that the required methods are implemented in each class.
Swift adds the ability to add these methods using extensions, and to use generic programming (generics) to implement them.
Combined, these allow protocols to be written once and support a wide variety of instances.
Also, the extension mechanism can be used to add protocol conformance to an object that does not list that protocol in its definition.
For example, a protocol might be declared called StringConvertible, which ensures that instances that conform to the protocol implement a toString method that returns a String.
In Swift, this can be declared with code like this:
protocol StringConvertible {     func toString() -> String }
This protocol can now be added to String, with no access to the base class's source:
extension String: StringConvertible {     func toString() -> String     {         self     } }
In Swift, like many modern languages supporting interfaces, protocols can be used as types, which means variables and methods can be defined by protocol instead of their specific type:
var someSortOfPrintableObject: StringConvertible ... print(someSortOfPrintableObject.toString())
It does not matter what sort of instance someSortOfPrintableObject is, the compiler will ensure that it conforms to the protocol and thus this code is safe.
This syntax also means that collections can be based on protocols also, like let printableArray = [StringConvertible].
As Swift treats structs and classes as similar concepts, both extensions and protocols are extensively used in Swift's runtime to provide a rich API based on structs.
For instance, Swift uses an extension to add the Equatable protocol to many of their basic types, like Strings and Arrays, allowing them to be compared with the == operator.
A concrete example of how all of these features interact can be seen in the concept of default protocol implementations:
func !
=<T : Equatable>(lhs: T, rhs: T) -> Bool
This function defines a method that works on any instance conforming to Equatable, providing a not equals function.
Any instance, class or struct, automatically gains this implementation simply by conforming to Equatable.
As many instances gain Equatable through their base implementations or other generic extensions, most basic objects in the runtime gain equals and not equals with no code.
This combination of protocols, defaults, protocol inheritance, and extensions allows many of the functions normally associated with classes and inheritance to be implemented on value types.
Properly used, this can lead to dramatic performance improvements with no significant limits in API.
This concept is so widely used within Swift that Apple has begun calling it a protocol-oriented programming language.
They suggest addressing many of the problem domains normally solved through classes and inheritance using protocols and structs instead.
Libraries, runtime and development
On Apple systems, Swift uses the same runtime as the extant Objective-C system, but requires iOS 7 or macOS 10.9 or higher.
It also depends on Grand Central Dispatch."
Do Swift-based apps work on macOS 10.9/iOS 7 and lower?", StackOverflow Swift and Objective-C code can be used in one program, and by extension, C and C++ also.
In contrast to C, C++ code cannot be used directly from Swift.
An Objective-C or C wrapper must be created between Swift and C++.
In the case of Objective-C, Swift has considerable access to the object model, and can be used to subclass, extend and use Objective-C code to provide protocol support."
Writing Swift Classes with Objective-C Behavior", Apple Inc.
The converse is not true: a Swift class cannot be subclassed in Objective-C.
To aid development of such programs, and the re-use of extant code, Xcode 6 and higher offers a semi-automated system that builds and maintains a bridging header to expose Objective-C code to Swift.
This takes the form of an additional header file that simply defines or imports all of the Objective-C symbols that are needed by the project's Swift code.
At that point, Swift can refer to the types, functions, and variables declared in those imports as though they were written in Swift.
Objective-C code can also use Swift code directly, by importing an automatically maintained header file with Objective-C declarations of the project's Swift symbols.
For instance, an Objective-C file in a mixed project called "MyApp" could access Swift classes or functions with the code #import "MyApp-Swift.h".
Not all symbols are available through this mechanism, however—use of Swift-specific features like generic types, non-object optional types, sophisticated enums, or even Unicode identifiers may render a symbol inaccessible from Objective-C."
Swift and Objective-C in the Same Project", Apple Inc.
Swift also has limited support for attributes, metadata that is read by the development environment, and is not necessarily part of the compiled code.
Like Objective-C, attributes use the @ syntax, but the currently available set is small.
One example is the @IBOutlet attribute, which marks a given value in the code as an outlet, available for use within Interface Builder (IB).
An outlet is a device that binds the value of the on-screen display to an object in code.
On non-Apple systems, Swift does not depend on an Objective-C runtime or other Apple system libraries; a set of Swift "Corelib" implementations replace them.
These include a "swift-corelibs-foundation" to stand in for the Foundation Kit, a "swift-corelibs-libdispatch" to stand in for the Grand Central Dispatch, and an "swift-corelibs-xctest" to stand in for the XCTest APIs from Xcode.
As of 2019, with Xcode 11, Apple has also added a major new UI paradigm called SwiftUI.
SwiftUI replaces the older Interface Builder paradigm with a new declarative development paradigm.
Memory management
Swift uses Automatic Reference Counting (ARC) to manage memory.
Apple used to require manual memory management in Objective-C, but introduced ARC in 2011 to allow for easier memory allocation and deallocation."
Automatic Reference Counting", Apple Inc.
One problem with ARC is the possibility of creating a strong reference cycle, where objects reference each other in a way that you can reach the object you started from by following references (e.g. A references B, B references A).
This causes them to become leaked into memory as they are never released.
Swift provides the keywords weak and unowned to prevent strong reference cycles.
Typically a parent-child relationship would use a strong reference while a child-parent would use either weak reference, where parents and children can be unrelated, or unowned where a child always has a parent, but parent may not have a child.
Weak references must be optional variables, since they can change and become nil.
A closure within a class can also create a strong reference cycle by capturing self references.
Self references to be treated as weak or unowned can be indicated using a capture list.
Debugging and other elements
A key element of the Swift system is its ability to be cleanly debugged and run within the development environment, using a read–eval–print loop (REPL), giving it interactive properties more in common with the scripting abilities of Python than traditional system programming languages.
The REPL is further enhanced with playgrounds, interactive views running within the Xcode environment that respond to code or debugger changes on-the-fly.
Playgrounds allow programmers to add in Swift code along with markdown documentation.
If some code changes over time or with regard to some other ranged input value, the view can be used with the Timeline Assistant to demonstrate the output in an animated way.
In addition, Xcode has debugging features for Swift development including breakpoints, step through and step over statements, as well as UI element placement breakdowns for app developers.
Apple says that Swift is "an industrial-quality programming language that's as expressive and enjoyable as a scripting language".About Swift, Apple Inc.
Performance
Many of the features introduced with Swift have well-known performance and safety trade-offs.
Apple has implemented optimizations that reduce this overhead.
Comparisons to other languages
Swift is considered a C family programming language and is similar to C in various ways:
Most C operators are used in Swift, but there are some new operators, for example to support integer operations with overflow (see under differences).
Curly braces are used to group statements.
Variables are assigned using an equals sign, but compared using two consecutive equals signs.
A new identity operator, ===, is provided to check if two data elements refer to the same object.
Control statements while, if, and switch are similar, but have extended functions, e.g., a switch that takes non-integer cases, while and if supporting pattern matching and conditionally unwrapping optionals, for uses the  syntax.
Square brackets are used with arrays, both to declare them and to get a value at a given index in one of them.
It also has similarities to Objective-C:
Basic numeric types (Int, UInt, Float, Double)
Class methods are inherited, like instance methods; self in class methods is the class the method was called on.
Similar for...in enumeration syntax.
Differences from Objective-C include:
Statements do not need to end with semicolons (;), though these must be used to allow more than one statement on a line.
No header files.
Uses type inference.
Generic programming.
Functions are first-class objects.
Enumeration cases can have associated data (algebraic data types).
Operators can be redefined for classes (operator overloading), and new operators can be defined.
Strings fully support Unicode.
Most Unicode characters can be used in either identifiers or operators.
No exception handling.
Swift 2 introduces a different and incompatible error-handling model.
Several features of earlier C-family languages that are easy to misuse have been removed:
Pointers are not exposed by default.
There is no need for the programmer to keep track of and mark names for referencing or dereferencing.
Assignments return no value.
This prevents the common error of writing i = 0 instead of i == 0 by throwing a compile-time error.
No need to use break statements in switch blocks.
Individual cases do not fall through to the next case unless the fallthrough statement is used.
Variables and constants are always initialized and array bounds are always checked.
Integer overflows, which result in undefined behavior for signed integers in C, are trapped as a run-time error in Swift.
Programmers can choose to allow overflows by using the special arithmetical operators &+, &-, &*, &/ and &%.
The properties min and max are defined in Swift for all integer types and can be used to safely check for potential overflows, versus relying on constants defined for each type in external libraries.
The one-statement form of if and while, which allows for the omission of braces around the statement, is unsupported.
C-style enumeration for (int i = 0; i < c; i++), which is prone to off-by-one errors, is unsupported (from Swift 3 onward).
The pre- and post- increment and decrement operators (i++, --i ...)
are unsupported (from Swift 3 onward), more so since C-style for statements are also unsupported from Swift 3 onward.
Development and other implementations
Since the language is open-source, there are prospects of it being ported to the web.
Some web frameworks have already been developed, such as IBM's Kitura, Perfect and Vapor.
An official "Server APIs" work group has also been started by Apple, with members of the Swift developer community playing a central role.
A second free implementation of Swift that targets Cocoa, Microsoft's Common Language Infrastructure (.NET), and the Java and Android platform exists as part of the Elements Compiler from RemObjects Software.
By combining toolchains from LLVM and Macintosh Programmer's Workshop, it is possible to run a very small subset of the language on Mac OS 9.
See also
Comparison of programming languages
Objective-C
Kotlin (programming language)
Python (programming language)
Nim (programming language)
References
External links
Swift at Apple Developer
Server-side Swift
Swift Example
Server-side Swift - The Vapor Framework
