Hello! When is your Swift Concurrency course released? It says it is still in progress. Thx

I know that you are using person name as an example code. But it should said that when dealing with with names that should use PersonNameComponentsFormatter as this will put the correct format for user locale

Thanks for the video. I concur. I would only add that, computed properties feel Swifty to me so I start with a bias towards using them, then change to a function when there's one of the situations that you've identified. (needs arguments, it's not lightweight, potential side-effects, etc)

Sound became better :) Could you please share your thoughts on usage of extensions, e.g. extending models with some methods, formatting methods etc. When an object that does something is better than extension of some model that handles the model certain way and returns the data I need, the only think that comes to my mind is inability to use DI in extension, so testability is limited for these functionality

your videos are so good man, top tier content! Keep it up :)

Nice generator. I have already added it to my new project so I do not forget it. Is it required for TestFlight?

Awesome, Is the required reasons API, the only thing that needs to be added? What about privacy nutrition labels? Let's say, my app uses email id info and Username. What do I do here?

Excelente video, muchas gracias por compartir información valiosa!!✌✌

🔥

Thanks @DonnyWalsdev! Great example and well explained.

I had to stop watching because of the background music - it’s not great when you’re narrating as I was unable to focus on what you were saying.

This is a great one. I was actually expecting to see another dictionary variable that keeps track of running tasks. But the enum with associated type looks so much better.

Subtle and complex! Thank you.

This is amazing, thank you for the explanation 🙏🏻 Can we have a video on task cancellation please?

This video is very helpful. I am still confused by the body property. As I understand it, Body is annotated via a protocol to run on MainActor. Is this correct: a view such as the one in your example that does not have a @MainActor annotation, but the function is called from a task modifier inside the Body will run on the MainActor.

the title was enough to trigger my anxiety😅

Can we have a sample project link ?

Thanks for the tip! Also these closures make use of withContinuation methods)

Nice video! Why not make a smaller protocol only giving the needed capability and then make the other protocol conform to the smaller if needed?

Thank for such great, simple but not trivial, examples!

Why can you input content in the canvas preview? How do I set it up?

I think makeStream is an anti-pattern because I ran into issues when using like cancellation not working. Once I redesigned my async code and made AsyncStream own the object that yields values all my problems were solved!

Thanks for this.

Earned a sub! This feels like talking to a coworker instead of watching a youtube video. THANKS!

🔥

I found very useful the idea of thinking that @State is telling SwiftUI who owns that object. I'll never forget that, thank you so much!

tickets are damn expensive for stuff that you find for free on UKposts...

This was very useful. Thanks.

Love these videos, keep them coming.

Your style of tutorial makes it more easier to understand Swift coding. Thanks a Lot !

would love to see concurrency playlist since you are the trusted person in dev community to learn hard topics .

Donny, how can I donate for a new mic :D. As a non-native speaker I need to be very concentrated on your voice to get the understanting.

Thanks for the video. Looking forward to more

Awesome, really well explained!

Thank you so much for this video, Donny! I have a question. You said we should use @State if the view owns the @Observable object. However, the following code works perfectly fine, even tough it was not marked with @State: @Observable class MyCounter { var count = 0 } struct ContentView: View { private let counter = MyCounter() var body: some View { VStack { Button(action: { counter.count += 1 }, label: { Text("Increment") }) Text("The counter is \(counter.count)") } } } You gave a great and clear explanation about the fact that we use @State if the object is within a view that is itself a subview, and we want to persist its value if the parent view updates. But let’s suppose we are sure the view from the example above won’t be a nested view. We also know that this view owns the object. But given the fact that everything works normally without using @State, is there really a good reason to use it besides the case when the object is in a subview and we don’t want to lose its value if a parent view updates? And thank you again for your video, it helps a lot.

Hey, nice video 🎉 should i use @observationIgnored property wrapper for non tracked properties in observable macro object ? Is observable macro handles itself ?

Lovely video overview, although your use of "we" and "you" when describing ownership and what's acting on what in comparing the differences was a bit confusing in places. I'm not yet using @Observable myself, more because of the brutal hit to compile time with macros, but I also want a shared observation publisher setup in a couple of places, which (as you mentioned near the end) Observable doesn't have anything to help with.

I wonder if this is working for you now. I'm getting the error "Return from initializer without initializing all stored properties" if I don't set movie in required init(from:)

Thank you for this video. The reason why an object can sometimes be a let and not a var has puzzled me, but thanks to your video I now understand why.

Btw what’s your xcode theme ? Looks very cool :)

If we are using @observable macro on our viewmodel, should we use @mainactor at the same time ?

That is why Apple will be pairing the new typed throws with the ErrorHandlerBuilder DSL. With the @ErrorHandlerBuilder decoration in our catch block we ... just kidding.

private var imageUrl: String? { didSet { dowloadImage() } } func setImage(_ imageUrl: String?, placeholder: UIImage?) { self.image = placeholder self.imageUrl = imageUrl } private func dowloadImage() { guard let imageUrl else { return } Task { @MainActor in do { let loadedImage = try await ImageLoader.shared.downloadImage(from: imageUrl) if imageUrl == self.imageUrl { image = loadedImage } } catch { debugPrint(error) } } } That’s the example of what I mean

Great video, thanks for sharing! And what about the assigning of the result of async func to UI-related piece? How exactly it works and should we care about main thread the same way as with gcd?

This is an interesting topic, thanks a ton for sharing!

Nicely explained. I would say the music is a little distracting and doesn't add anything IMO.