All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Understanding Swift's @isolated(any) Attribute for Async Concurrency Control

By

peterspath

9mo ago· 9 min readenInsight

Summary

This article explains the Swift programming language's @isolated(any) attribute, introduced to provide more visibility and control over scheduling asynchronous work. It discusses the contradictions and nuances of the attribute, including that it must always take an argument but that argument cannot vary. The article connects @isolated(any) to async functions and explores how it gives developers finer control over concurrency in Swift.

Key quotes

· 5 pulled
Ahh, @isolated(any). It's an attribute of contradictions.
You might see it a lot, but it's ok to ignore it.
You don't need to use it, but I think it should be used more.
It must always take an argument, but that argument cannot vary.
There are cases where just a little more visibility and control over how to schedule asynchronous work can make all the difference.
Snippet from the RSS feed
There are cases where just a little more visibility and control over how to schedule asynchronous work can make all the difference.

You might also wanna read