How to use Actors and non-isolated in Swift | Swift Concurrency #9
Вставка
- Опубліковано 22 сер 2024
- 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 UA-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🥺
Best swift tutorials ever
So valuable content. Thank you so much Nick!!! you are a great teacher
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!
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?
Amazing, just learned something new today. Thanks for teaching us!
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.
19:01 Start of discussion about actors.
Hi Nick, this was the one i was looking for. Thanks for everything
Great explanation! Thank you Nick
Wonderful! Thank you 😆
very nice explanation
I know this wasn't the point of the video but the lock.async closure should have a weak reference to self right?
Bravo man
You are the best!!❤
Video is great, but Nick forgot to mention that 'Thread Sanitizer' option is NOT available for ALL devices
awsome as always
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
Good explenation. Thank you!
Nice. Now use combine to publish the string automagically by subscribing to the timer and mapping it...
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
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?
This is awesome 👏
thanks a lot!😍
thanks a lot as always~~~!!!
Hey Nick! great content! Can race conditions occur within the same class by using a task group? How to handle this?
Hi, thanks for the video! Where can the code in the videos be found?
Crazy content, do you also do mentoring?
In Xcode 14 we get an error as we should .