How to use Actors and non-isolated in Swift | Swift Concurrency #9
ฝัง
- เผยแพร่เมื่อ 9 ก.พ. 2025
- Actors are possibly the most important update to come out of Swift Concurrency! They are incredibly powerful and solve Data Race problems in our applications! This is crucially important when working in a multi-threaded environment! In this video we will learn:
1) The problem that Actors solve
2) How to solve the problem without Actors
3) How to solve the problem with Actors!
Next video: • How to use Global Acto...
Previous video: • Swift: Struct vs Class...
🤙 WELCOME BACK 🤙
WEBSITE: www.swiftful-t...
DISCORD: / discord
GITHUB: github.com/Swi...
SAY THANKS: www.buymeacoff...
The fact that you are giving this content away for free on TH-cam is amazing! This was an awesome video, didn't know what non isolated was before this
Awesome video. Best explanation I’ve seen so far for when to use Actors 🙌🏻
This was amazing.Please post more videos on swift and swiftUI🥺
Again a nice and easy to understand video. I'm looking forward to the next one.
Good explication of no isolated and example of differences between actors and classes, thanks!
Excellent tutorials. I really wanna watch the last 3 videos in this playlist now!
So valuable content. Thank you so much Nick!!! you are a great teacher
Best swift tutorials ever
Hi Nick, this was the one i was looking for. Thanks for everything
Amazing, just learned something new today. Thanks for teaching us!
Great explanation! Thank you Nick
At 6:40 you mention that you have a whole video where to talk about why you don't recommend using singleton's? Could you point me to that video? I'm curious to learn more!
The solution to not using Singletons is usually using Dependency Injection. More info:
How to use Dependency Injection in SwiftUI | Advanced Learning #16
th-cam.com/video/E3x07blYvdE/w-d-xo.html
@@SwiftfulThinking Awesome, thanks! I'll give it a look :)
Awesome Content!
HI Nick
Can you please make a video on what are the different ways of designing a data manager class with their pros and cons?
You are the best!!❤
awsome as always
Wonderful! Thank you 😆
very nice explanation
Good explenation. Thank you!
It's important to notice that we should use a serial queue, which is the default in Swift, but was not the case for Objective-C.
11:21 I'm probably misunderstanding, but is this really needed to do on a different background thread? Isn't it this doing it on a different background *queue*? And the queue will, under the hood, choose which thread to use?
Thank you for all these swiftUI tutorials...I've seen almost all of them, I learned a lot and I hope you will take other courses....I'm curious what you think also about flutter and if you' have seen it, I noticed some similarities with SwiftUI
Video is great, but Nick forgot to mention that 'Thread Sanitizer' option is NOT available for ALL devices
This is awesome 👏
Hey Nick! great content! Can race conditions occur within the same class by using a task group? How to handle this?
Bravo man
Thanks! Just one question here:
1. How your code becomes threads safe when you add asynchronous queue ? I think there should be serial queue.
Could you please explain here? Thanks again for amazing videos
Ahh, I see default init for DespatchQueue returns serial queue
Hi man, I saw you commented here and I have the same question why using async queue to make thread safe? As my understanding the queue.sync {} can make it serial executed. Am I making something misunderstanding here?
thanks a lot!😍
Crazy content, do you also do mentoring?
19:01 Start of discussion about actors.
Nice. Now use combine to publish the string automagically by subscribing to the timer and mapping it...
thanks a lot as always~~~!!!
I know this wasn't the point of the video but the lock.async closure should have a weak reference to self right?
In Xcode 14 we get an error as we should .