3 MISTAKES to avoid when using Async / Await in Swift 😌 

⚠ There's a a slight mistake at 04:10: while it's true that the `Task.detached` won't be canceled, it would have also been the same for a regular `Task`. ⚠

Tip #2 was really good, Vincent! I never thought about where to place the guard let self. Thanks for sharing!

This is one of the most eloquent and succinct coding explanations I have found to date. Très cordialement

Yesterday, i learned retain cycle from your previous videos. Today I try the Tip #2 in new sample project and I realized that the ViewModel not delocating from memory if we use the listenNotifications method as the first example. I check the ViewModel class allocation in memorygraph with everysteps to learn what's going on in the memory. Thank's for this valuable post for us !

Thanks for the video! I have a question about point 2 of the video. Does creating the async stream has different effect on memory when created outside of the Task closure or inside?

What if I need to reference self. before loop? like: for await value in self.manager.$items.values {...}

4:10 Are you sure that a Task (A simple Task, without detached) inside a Task will cancel in a cascade way?

nice

Tip #1 is interesting, however in case the refresh token is expired, it would cause a double request to get a new one. How can we avoid this with?