Through version 3.0 the syntax of Swift went through significant evolution, with the core team making source stability a focus in later versions.[17][18] In the first quarter of 2018 Swift surpassed Objective-C in measured popularity.[19]
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.[20]
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.[21]
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.[22]
Swift 5.9, was released in September 2023 and includes a macro system, generic parameter packs, and ownership features like the new consume operator.[23]
The current version, Swift 5.10, was released in March 2024. This version improves the language's concurrency model, allowing for full data isolation to prevent data races. It is also the last release before Swift 6.[24] Version 5.10 is currently available for macOS, Windows and, in experimental use, for Linux.[25]
History
Development of Swift started in July 2010 by Chris Lattner, with the eventual collaboration of many other programmers at Apple. Swift was motivated by the need for a replacement for Apple's earlier programming language Objective-C, which had been largely unchanged since the early 1980s and lacked modern language features. Swift took language ideas "from Objective-C, Rust, Haskell, Ruby, Python, C#, CLU, and far too many others to list".[7] On June 2, 2014, the Apple Worldwide Developers Conference (WWDC) application became the first publicly released app written with Swift.[26] 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.[26]
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.[27]
Swift reached the 1.0 milestone on September 9, 2014, with the Gold Master of Xcode 6.0 for iOS.[28] Swift 1.1 was released on October 22, 2014, alongside the launch of Xcode 6.1.[29] Swift 1.2 was released on April 8, 2015, along with Xcode 6.3.[30] Swift 2.0 was announced at WWDC 2015, and was made available for publishing apps in the App Store on September 21, 2015.[31] Swift 3.0 was released on September 13, 2016.[32] Swift 4.0 was released on September 19, 2017.[33] Swift 4.1 was released on March 29, 2018.[34]
Swift won first place for Most Loved Programming Language in the Stack Overflow Developer Survey 2015[35] and second place in 2016.[36]
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,[37] 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.[38][39][40] The Swift Sandbox was deprecated in January 2018.[41]
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.[42][43][44]
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.[45][46]
During WWDC 2019, Apple announced SwiftUI with Xcode 11, which provides a framework for declarative UI structure design across all Apple platforms.[47]
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.[48] There is an unofficial SDK and native toolchain package for Android too.[49][50]
A key aspect of Swift's design is its ability to interoperate with the huge body of existing Objective-C code developed for Apple products over the previous decades, such as Cocoa and the Cocoa Touchframeworks. On Apple platforms,[53] it links with the Objective-C runtime library, which allows C, Objective-C, C++ and Swift code to run within one program.[54]
Swift is a general purpose programming language that employs modern programming-language theory concepts and strives to present a simple, yet powerful syntax. Swift incorporates innovations and conventions from various programming languages, with notable inspiration from Objective-C, which it replaced as the primary development language on Apple Platforms.
Swift was designed to be safe and friendly to new programmers while not sacrificing speed. By default Swift manages all memory automatically and ensures variables are always initialized before use. Array accesses are checked for out-of-bounds errors and integer operations are checked for overflow. Parameter names allow creating clear APIs. Protocols define interfaces that types may adopt, while extensions allow developers to add more function to existing types. Swift enables object-oriented programming with the support for classes, subtyping, and method overriding. Optionals allow nil values to be handled explicitly and safely. Concurrent programs can be written using async/await syntax and actors isolate shared mutable state in order to eliminate data races.[70][71]
Basic syntax
Swift's syntax is similar to C-style languages. Code begins executing in the global scope by default.[72] Alternatively, the @main attribute can be applied a structure, class, or enumeration declaration to indicate that it contains the program's entry point.[73]
The print(_:separator:terminator:) function used here is included in Swift's standard library, which is available to all programs without the need to import external modules. Statements in Swift don't have to end with a semicolon, however semicolons are required to separate multiple statements written on the same line. Single-line comments begin with // and continue until the end of the current line. Multiline comments are contained by /* and */ characters.
Constants are declared with the let keyword and variables with the var keyword. Values must be initialized before they are read. Values may infer their type based on the type of the provided initial value. If the initial value is set after the value's declaration, a type must be declared explicitly.[72]
lethighScoreThreshold=1000// A constant with type Int. The type was inferred based on the provided value.varcurrentScore=980// A variable with type Int.currentScore=1200// The value of variables can change over time.letplayerMessage:String// A constant with explicit type String.ifcurrentScore>highScoreThreshold{playerMessage="You are a top player!"}else{playerMessage="Better luck next time."}print(playerMessage)// Prints "You are a top player!"
Control flow in Swift is managed with if-else, guard, and switch statements, along with while and for-in loops.
If statements take a boolean parameter and execute the body of the if statement if the condition is true, otherwise it executes the optional else body. if-let syntax provides syntactic sugar for checking for the existence of an optional value and unwrapping it at the same time.
letsomeNumber=42ifsomeNumber%2==0{// Use the remainder operator to find the remainder of someNumber divided by 2.print("\(someNumber) is even.")}else{print("\(someNumber) is odd.")}// Prints "42 is even."
Functions are defined with the func keyword. Function parameters may have names which allow function calls to read like phrases. An underscore before the parameter name allows the argument label to be omitted from the call site. Tuples can be used by functions to return multiple pieces of data at once.
funcconstructGreeting(forname:String)->String{return"Hello \(name)!"}letgreeting=constructGreeting(for:"Craig")print(greeting)// Prints "Hello Craig!"
Functions, and anonymous functions known as closures, can be assigned to properties and passed around the program like any other value.
funcdivideByTwo(_aNum:Int)->Int{returnaNum/2}funcmultiplyByTwo(_aNum:Int)->Int{returnaNum*2}letmathOperation=multiplyByTwoprint(mathOperation(21))// Prints "42"
guard statements require that the given condition is true before continuing on past the guard statement, otherwise the body of the provided else clause is run. The else clause must exit control of the code block in which the guard statement appears. guard statements are useful for ensuring that certain requirements are met before continuing on with program execution. In particular they can be used to create an unwrapped version of an optional value that is guaranteed to be non-nil for the remainder of the enclosing scope.
funcdivide(numerator:Int?,byDenominatordenominator:Int)->Int?{guarddenominator!=0else{print("Can't divide by 0.")returnnil}guardletnumeratorelse{print("The provided numerator is nil.")returnnil}returnnumerator/denominator}letresult=divide(numerator:3,byDenominator:0)print("Division result is: \(result)")// Prints:// "Can't divide by 0."// "Division result is: nil."
switch statements compare a value with multiple potential values and then executes an associated code block. switch statements must be made exhaustive, either by including cases for all possible values or by including a default case which is run when the provided value doesn't match any of the other cases. switch cases do not implicitly fall through, although they may explicitly do so with the fallthrough keyword. Pattern matching can be used in various ways inside switch statements. Here is an example of an integer being matched against a number of potential ranges:
letsomeNumber=42switchsomeNumber{case..<0:print("\(someNumber) negative.")case0:print("\(someNumber) is 0.")case1...9:print("\(someNumber) greater than 0, but less than 10.")default:print("\(someNumber) is greater than 9.")}// Prints "42 is greater than 9."
while loops iterate as long as the given boolean condition evaluates to true:
// Add together all the numbers from 1 to 5.vari=1varresult=0whilei<=5{// The loop performs its body as long as i is less than or equal to 5. result+=i// Add i to the current result.i+=1// Increment i by 1.}print(result)// Prints "15"
Closure support
Swift supports closures, which are self-contained blocks of functionality that can be passed around and used in code,[74] and can also be used as anonymous functions. Here are some examples:
// Closure type, defined by its input and output values, can be specified outside the closure:letclosure1:(Int,Int)->Int={arg1,arg2inreturnarg1+arg2}// …or inside it:letclosure2={(arg1:Int,arg2:Int)->Intinreturnarg1+arg2}// In most cases, closure's return type can be inferred automatically by the compiler.letclosure3={arg1:Int,arg2:Intinreturnarg1+arg2}
Closures can be assigned to variables and constants, and can be passed into other functions or closures as parameters. Single-expression closures may drop the return keyword.
Swift also has a trailing closure syntax, which allows the closure to be written after the end of the function call instead of within the function's parameter list. Parentheses can be omitted altogether if the closure is the function's only parameter:
// 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.funcfoo(closurebar:()->Int)->Int{returnbar()}// Without trailing closure syntax:foo(closure:{return1})// With trailing closure syntax, and implicit return:foo{1}
Starting from version 5.3, Swift supports multiple trailing closures:[75]
// This function passes the return of the first closure as the parameter of the second,// and returns the second closure's result:funcfoo(bar:()->Int,baz:(Int)->Int)->Int{returnbaz(bar())}// With no trailing closures:foo(bar:{return1},baz:{xinreturnx+1})// With 1 trailing closure:foo(bar:{return1}){xinreturnx+1}// With 2 trailing closures (only the first closure's argument name is omitted):foo{return1}baz:{xinreturnx+1}
Swift will provide shorthand argument names for inline closures, removing the need to explicitly name all of the closures parameters.[76] Arguments can be referred to with the names $0, $1, $2, and so on:
letnames=["Josephine","Steve","Chris","Barbara"]// filter calls the given closure for each value in names. // Values with a character count less than 6 are kept, the others are dropped.letshortNames=names.filter{$0.count<6}print(shortNames)// Prints "["Steve", "Chris"]"
Closures may capture values from their surrounding scope. The closure will refer to this captured value for as long as the closure exists:
funcmakeMultiplier(withMultiplemultiple:Int)->(Int)->(Int){// Create and return a closure that takes in an Int and returns the input multiplied by the value of multiple.return{$0*multiple}}letmultiplier=makeMultiplier(withMultiple:3)print(multiplier(3))// Prints "9"print(multiplier(10))// Prints "30"
String support
The Swift standard library includes unicode-compliant String and Character types. String values can be initialized with a String literal, a sequence of characters surrounded by double quotation marks. Strings can be concatenated with the + operator:
varsomeString="Hello,"someString+=" world!"
String interpolation allows for the creation of a new string from other values and expressions. Values written between parentheses preceded by a \ will be inserted into the enclosing string literal:[77]
varcurrentScore=980print("Your score is \(currentScore).")// Prints "Your score is 980."
A for-in loop can be used to iterate over the characters contained in a string:
forcharacterin"Swift"{print(character)}// S// w// i// f// t
When the Foundation framework is imported Swift invisibly bridges the String type to NSString, the String class commonly used in Objective-C.
In Swift, callable objects are defined using callAsFunction.[78]
structCallableStruct{varvalue:IntfunccallAsFunction(_number:Int,scale:Int){print(scale*(number+value))}}letcallable=CallableStruct(value:100)callable(4,scale:2)callable.callAsFunction(4,scale:2)// Both function calls print 208.
Access control
Swift supports five access control levels for symbols: open, public, internal, fileprivate, and private. Unlike many object-oriented languages, these access controls ignore inheritance hierarchies: private indicates that a symbol is accessible only in the immediate scope, fileprivate indicates it is accessible only from within the file, internal indicates it is accessible within the containing module, public indicates it is accessible from any module, and open (only for classes and their methods) indicates that the class may be subclassed outside of the module.[79]
Optionals and chaining
An important 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 either refer to a specific value or no value at all. 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 enum. To make an Integer that is nullable, one would use a declaration similar to var optionalInteger: Optional<Int>. As in C#,[80] 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?.[81] 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 former is of type String while the latter is an Optional that may be holding some String value.
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:
letmyValue=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, terminating the program. This is known as force unwrapping. Optionals may be safely unwrapped using optional chaining which first tests whether the instance is nil, and then unwrap it if it is non-null:
letmyValue=anOptionalInstance?.someMethod()
In this case the runtime calls someMethod only if anOptionalInstance is not nil, suppressing the error. A ? must be placed after every optional property. If any of these properties are nil the entire expression evaluates as nil. The origin of the term chaining comes from the more common case where several method calls/getters are chained together. For instance:
Swift's use of optionals allows the compiler to use static dispatch because the unwrapping action is called on a defined instance (the wrapper), versus occurring in a 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.
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.[82]
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 indirection or reference counting. 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.[82] Using value types can result in significant performance improvements in user applications as well.[83]
Array, Dictionary, and Set all utilize copy on write so that their data 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.[84]
Extensions
Extensions add new functionality to an existing type, without the need to subclass or even have access to the original source code. Extensions can add new methods, initializers, computed properties, subscripts, and protocol conformances.[85] An example might be to add a spell checker to the base String type, which means all instances of String in the program gain the ability to spell-check. The system is also widely used as an organizational technique, allowing related code to be gathered into library-like extensions.
Extensions are declared with the extension keyword.
Protocols promise that a particular type implements a set of methods or properties, meaning that other instances in the system can call those methods on any instance implementing that protocol. This is often used in modern object-oriented languages as a substitute for multiple inheritance, although the feature sets are not entirely similar.
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.[86] 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.[87]
For example, a protocol might be declared called Printable, which ensures that instances that conform to the protocol implement a description property and a printDetails() method requirement:
// Define a protocol named PrintableprotocolPrintable{vardescription:String{get}// A read-only property requirementfuncprintDetails()// A method requirement}
This protocol can now be adopted by other types:
// Adopt the Printable protocol in a classclassMyClass:Printable{vardescription:String{return"An instance of MyClass"}funcprintDetails(){print(description)}}
Extensions can be used to add protocol conformance to types. Protocols themselves can also be extended to provide default implementations of their requirements. Adopters may define their own implementations, or they may use the default implementation:
extensionPrintable{// All Printable instances will receive this implementation, or they may define their own.funcprintDetails(){print(description)}}// Bool now conforms to Printable, and inherits the printDetails() implementation above.extensionBool:Printable{vardescription:String{return"An instance of Bool with value: \(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:
funcgetSomethingPrintable()->anyPrintable{returntrue}varsomeSortOfPrintableInstance=getSomethingPrintable()print(someSortOfPrintableInstance.description)// Prints "An instance of Bool with value: true"
It does not matter what concrete type of someSortOfPrintableInstance 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 = [any Printable].
Both extensions and protocols are used extensively in Swift's standard library; in Swift 5.9, approximately 1.2 percent of all symbols within the standard library were protocols, and another 12.3 percent were protocol requirements or default implementations.[88] For instance, Swift uses extensions to add the Equatable protocol to many of their basic types, like Strings and Arrays, allowing them to be compared with the == operator. The Equatable protocol also defines this default implementation:
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 operator. Any instance, class or struct, automatically gains this implementation simply by conforming to Equatable.[89]
Protocols, extensions, and generics can be combined to create sophisticated APIs. For example, constraints allow types to conditionally adopt protocols or methods based on the characteristics of the adopting type. A common use case may be adding a method on collection types only when the elements contained within the collection are Equatable:
extensionArraywhereElement:Equatable{// allEqual will be available only on instances of Array that contain Equatable elements. funcallEqual()->Bool{forelementinself{ifelement!=self.first{returnfalse}}returntrue}}
Concurrency
Swift 5.5 introduced structured concurrency into the language.[90] Structured concurrency uses Async/await syntax similar to Kotlin, JavaScript, and Rust. An async function is defined with the async keyword after the parameter list. When calling an async function the await keyword must be written before the function to indicate that execution will potentially suspend while calling function. While a function is suspended the program may run some other concurrent function in the same program. This syntax allows programs to clearly call out potential suspension points and avoid a version of the Pyramid of doom (programming) caused by the previously widespread use of closure callbacks.[91]
funcdownloadText(name:String)async->String{letresult=// ... some asynchronous downloading code ...returnresult}lettext=awaitdownloadText("text1")
The async let syntax allows multiple functions to run in parallel. await is again used to mark the point at which the program will suspend to wait for the completion of the async functions called earlier.
// Each of these calls to downloadText will run in parallel.asynclettext1=downloadText(name:"text1")asynclettext2=downloadText(name:"text2")asynclettext3=downloadText(name:"text3")lettextToPrint=await[text1,text2,text3]// Suspends until all three downloadText calls have returned.print(textToPrint)
Tasks and TaskGroups can be created explicitly to create a dynamic number of child tasks during runtime:
Swift uses the Actor model to isolate mutable state, allowing different tasks to mutate shared state in a safe manner. Actors are declared with the actor keyword and are reference types, like classes. Only one task may access the mutable state of an actor at the same time. Actors may access and mutate their own internal state freely, but code running in separate tasks must mark each access with the await keyword to indicate that the code may suspend until other tasks finish accessing the actor's state.
actorDirectory{varnames:[String]=[]funcadd(name:String){names.append(name)}}letdirectory=Directory()// Code suspends until other tasks finish accessing the actor.awaitdirectory.add(name:"Tucker")print(awaitdirectory.names)
Libraries, runtime, 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.[92] Swift and Objective-C code can be used in one program, and by extension, C and C++ also. Beginning in Swift 5.9, C++ code can be used directly from Swift code.[93] 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.[94] The converse is not true: a Swift class cannot be subclassed in Objective-C.[95]
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.[96]
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.[97]
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.[98]
Memory management
Swift uses Automatic Reference Counting (ARC) to manage memory. Every instance of a class or closure maintains a reference count which keeps a running tally of the number of references the program is holding for on to. When this count reaches 0 the instance is deallocated. This automatic deallocation removes the need for a garbage collector as instances are deallocated as soon as they are no longer needed.
A strong reference cycle can occur if two instances each strongly reference each other (e.g. A references B, B references A). Since neither instances reference count can ever reach zero neither is ever deallocated, resulting in a memory leak. Swift provides the keywords weak and unowned to prevent strong reference cycles. These keywords allow an instance to be referenced without incrementing its reference count. weak references must be optional variables, since they can change and become nil.[99] Attempting to access an unowned value that has already been deallocated results in a runtime error.
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.
classPerson{letname:Stringweakvarhome:Home?// Defined as a weak reference in order to break the reference cycle. weak references do not increment the reference count of the instance that they refer to.init(name:String){self.name=name}deinit{print("De-initialized \(name)")}}classHome{letaddress:Stringvarowner:Person?init(address:String,owner:Person?){self.address=addressself.owner=owner}deinit{print("De-initialized \(address)")}}varstacy:Person?=Person(name:"Stacy")varhouse21b:Home?=Home(address:"21b Baker Street",owner:stacy)stacy?.home=house21b// stacy and house42b now refer to each other.stacy=nil// The reference count for stacy is now 1, because house21b is still holding a reference to it. house21b=nil// house21b's reference count drops to 0, which in turn drops stacy's count to 0 because house21b was the last instance holding a strong reference to stacy.// Prints:// De-initialized 21b Baker Street// De-initialized Stacy
Debugging
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 or Playgrounds app that respond to code or debugger changes on-the-fly.[100] Playgrounds allow programmers to add in Swift code along with markdown documentation. Programmers can step through code and add breakpoints using LLDB either in a console or an IDE like Xcode.
Most operators in C also appear in Swift, although some operators such as + have slightly different behavior. For example, in Swift, + traps on overflow, whereas &+ is used to denote the C-like behavior of wrapping on overflow.
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 foriin1...10 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 need not end with semicolons (;), though these must be used to allow more than one statement on one line.
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.[101]
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).[102]
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.[103]
Development and other implementations
Because Swift can run on Linux, it is sometimes also used as a server-side language.[104] Some web frameworks have already been developed, such as IBM's Kitura (now discontinued), Perfect and Vapor.
An official "Server APIs" work group has also been started by Apple,[105] with members of the Swift developer community playing a central role.[106]
^"Chris Lattner's Homepage". Chris Lattner. June 3, 2014. Retrieved June 3, 2014. The Swift language is the product of tireless effort from a team of language experts, documentation gurus, compiler optimization ninjas, and an incredibly important internal dogfooding group who provided feedback to help refine and battle-test ideas. Of course, it also greatly benefited from the experiences hard-won by many other languages in the field, drawing ideas from Objective-C, Rust, Haskell, Ruby, Python, C#, CLU, and far too many others to list.
^ abLattner, Chris (June 3, 2014). "Chris Lattner's Homepage". Chris Lattner. Retrieved June 3, 2014. I started work on the Swift Programming Language in July of 2010. I implemented much of the basic language structure, with only a few people knowing of its existence. A few other (amazing) people started contributing in earnest late in 2011, and it became a major focus for the Apple Developer Tools group in July 2013 [...] drawing ideas from Objective-C, Rust, Haskell, Ruby, Python, C#, CLU, and far too many others to list.
^"Extensions". docs.swift.org. Retrieved November 28, 2023.
^"Working with Protocols". Programming with Objective-C. Apple Developer Documentation Archive. September 17, 2014. Archived from the original on April 29, 2016.
