{"id":36261,"date":"2022-06-17T15:49:22","date_gmt":"2022-06-17T19:49:22","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=36261"},"modified":"2022-07-06T14:25:18","modified_gmt":"2022-07-06T18:25:18","slug":"swift-5-7-announced","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/06\/17\/swift-5-7-announced\/","title":{"rendered":"Swift 5.7 Announced"},"content":{"rendered":"

What’s new in Swift<\/a>:<\/p>\n

We’ll take you through performance improvements, explore more secure and extensible Swift packages, and share advancements in Swift concurrency. We’ll also introduce you to Swift Regex, better generics, and other tools built into the language to help you write more flexible & expressive code.<\/p><\/blockquote>\n\n

Embrace Swift generics<\/a>:<\/p>\n

Generics are a fundamental tool for writing abstract code in Swift. Learn how you can identify opportunities for abstraction as your code evolves, evaluate strategies for writing one piece of code with many behaviors, and discover language features in Swift 5.7 that can help you make generic code easier to write and understand.<\/p><\/blockquote>\n\n

Design protocol interfaces in Swift<\/a>:<\/p>\n

Learn how you can use Swift 5.7 to design advanced abstractions using protocols. We’ll show you how to use existential types, explore how you can separate implementation from interface with opaque result types, and share the same-type requirements that can help you identify and guarantee relationships between concrete types<\/p><\/blockquote>\n\n

Meet distributed actors in Swift<\/a>:<\/p>\n

Discover distributed actors — an extension of Swift’s actor model that simplifies development of distributed systems. We’ll explore how distributed actor isolation and location transparency can help you avoid the accidental complexity of networking, serialization, and other transport concerns when working with distributed apps and systems.<\/p><\/blockquote>\n\n

Visualize and optimize Swift concurrency<\/a>:<\/p>\n

Learn how you can optimize your app with the Swift Concurrency template in Instruments. We’ll discuss common performance issues and show you how to use Instruments to find and resolve these problems. Learn how you can keep your UI responsive, maximize parallel performance, and analyze Swift concurrency activity within your app.<\/p><\/blockquote>\n\n

Eliminate data races using Swift Concurrency<\/a>:<\/p>\n

Join us as we explore one of the core concepts in Swift concurrency: isolation of tasks and actors. We’ll take you through Swift’s approach to eliminating data races and its effect on app architecture. We’ll also discuss the importance of atomicity in your code, share the nuances of Sendable<\/code> checking to maintain isolation, and revisit assumptions about ordering work in a concurrent system.<\/p><\/blockquote>\n\n

Meet Swift Async Algorithms<\/a>:<\/p>\n

Discover the latest open source Swift package from Apple: Swift Async Algorithms. We’ll explore algorithms from this package that you can use with AsyncSequence<\/code>, including zip<\/code>, merge<\/code>, and throttle<\/code>. Follow along with us as we use these algorithms to build a great messaging app. We’ll also share best practices for combining multiple AsyncSequences<\/code> and using the Swift Clock<\/code> type to work with values over time.<\/p><\/blockquote>\n\n

• • •<\/p>\n\n

Slava Pestov<\/a>:<\/p>\n

Xcode 14 ships with Swift 5.7, which brings massive improvements to generics and protocols! 🧵<\/p><\/blockquote>\n\n

John Sundell<\/a>:<\/p>\n

\n

Swift 5.7 introduces a new, more concise way to unwrap optional values using if let<\/code> and guard let<\/code> statements.<\/p>\n<\/blockquote>\n\n

Donny Wals<\/a>:<\/p>\n

\n

While it sounds like the any<\/code> keyword acts as a type erasing<\/a> helper, all it really does is inform the compiler that you opt-in to using an existential (a box type that conforms to a protocol) as your type.<\/p>\n<\/blockquote>\n\n

Donny Wals<\/a>:<\/p>\n

\n

In Swift 5.7, protocols can specify primary associated types. These associated types are a lot like generics. They allow developers to specify the type for a given associated type as a generic constraint.<\/p>\n<\/blockquote>\n\n

John Sundell<\/a>:<\/p>\n

\n

Thankfully, this is a problem that Swift 5.7 neatly solves by expanding the some<\/code> keyword (that was introduced back in Swift 5.1) to also be applicable to function arguments.<\/p>\n

[…]<\/p>\n

Swift 5.7 once again introduces a much more lightweight way to express the above kind of declaration, which works the exact same way as when specializing a concrete<\/em> generic type (such as Array<Article><\/code>). That is, we now can simply tell the compiler what Element<\/code> type that we’d like our input Collection<\/code> to contain by adding that type within angle brackets right after the protocol name[…]<\/p>\n<\/blockquote>\n\n

Marcin Krzyzanowski<\/a>:<\/p>\n

\n

“Any UIKit subclass that uses deinit<\/code> now essentially causes warnings<\/a> in Swift 5.7 while they are never touched on other threads anyways.”<\/p>\n<\/blockquote>\n\n

Karoy<\/a> Lorentey<\/a>:<\/p>\n

(Set<\/code> now uses the new Temporary Buffers feature to make operations like intersect<\/code> up to 4-6x faster.<\/p><\/blockquote>\n\n

Previously:<\/p>\n