This week's SwiftLee Weekly covers:

• Default Isolation in Swift 6.2
• The .ignoredByLayout() modifier in SwiftUI
• Optimizing Mathematical Computations in Swift

Enjoy this week's SwiftLee Weekly!

THIS WEEK'S BLOG POST

​Institutional Purchases: Understanding and Detecting​

Recently, I discovered a spike in total downloads of 25K installs. Yet, I did not see an unusual spike in trials or purchases. I decided to dive in and found out it was caused by something called Institutional Purchases.

SPONSORED

​Fastlane alternative - Codemagic CLI tools​

Are you tired of Ruby and Fastlane installation issues? There's got to be a better way! Discover Codemagic open source CLI tools. It is not a drop-in replacement for all of what Fastlane does (screenshots for example), but we use it at Codemagci to build and publish iOS and Android apps, also versioning and device provisioning. View on GitHub.

SWIFT EVOLUTION

An overview of last week's Swift Proposal state changes. Check them out when they're in review, as it's your opportunity to influence the direction of Swift's future.

CODE SNIPPET OF THE WEEK

Constant Binding in SwiftUI

You can find this post on Twitter/X, LinkedIn, or Bluesky.

Antoine v.d. SwiftLee  @twannl A constant binding in SwiftUI can be helpful when quickly prototyping your views 🚀 5:54 PM • May 19, 2025 3 Retweets 26 Likes Read 3 replies

​

QUESTION OF THE WEEK

Combine has not received many updates over the past years and it seems that Apple is slowly moving away from it too with the introduction of @Observable. Yet, there has not been an obvious replacement to observe values as we know from Combine.

There are ways to use AsyncStream to create a similar pipeline, but it comes with limitations like having only a single subscriber.

​Apple's open-sourced Async Algorithms framework comes with methods you'll recognize from Combine pipelines, but it's the AsyncExtensions package that will give you classes like AsyncPassthroughSubject which will be closer to what you use in Combine.

I also want to highlight Swift Evolution Proposal SE-475: Transactional Observation of Values which is currently in Active Review. It's not a Combine replacement, but it will be a useful tool in case it gets implemented into a future version of Swift.

Finally, I've not found myself using Combine pipelines a lot lately. Debouncing and throtthling can be done via Swift Concurrency (learn about it here) and observing values is something I do using SwiftUI bindings. Whether these use Combine under the hood or not: I'll let Apple decide and make my code future proof.