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?
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
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?
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
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
Best swift tutorials ever
This was amazing.Please post more videos on swift and swiftUI🥺
Good explication of no isolated and example of differences between actors and classes, thanks!
Awesome video. Best explanation I’ve seen so far for when to use Actors 🙌🏻
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.
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?
Excellent tutorials. I really wanna watch the last 3 videos in this playlist now!
Amazing, just learned something new today. Thanks for teaching us!
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?
Hi Nick, this was the one i was looking for. Thanks for everything
Hey Nick! great content! Can race conditions occur within the same class by using a task group? How to handle this?
very nice explanation
Awesome Content!
I know this wasn't the point of the video but the lock.async closure should have a weak reference to self right?
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?
Great explanation! Thank you Nick
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
Wonderful! Thank you 😆
Crazy content, do you also do mentoring?
awsome as always
19:01 Start of discussion about actors.
You are the best!!❤
Bravo man
Good explenation. Thank you!
Video is great, but Nick forgot to mention that 'Thread Sanitizer' option is NOT available for ALL devices
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.
Nice. Now use combine to publish the string automagically by subscribing to the timer and mapping it...
thanks a lot!😍
This is awesome 👏
thanks a lot as always~~~!!!
In Xcode 14 we get an error as we should .