I'm glad you liked it

Thanks Ahmad 😊

Thanks, Akshay 😊

That’s awesome! 😊

It’s my pleasure 😊

Thank you 😊

Thanks, Sahhar 😊

Thanks, Waqas 😊

Thanks bro

I'm glad you liked it 😊

Thanks 😊

Great question, Ray. First, code is executed line by line. If a line takes more time to execute, it delays the execution of the rest. Second, “save” will crash if it runs first because our save method uses a resource that’s not yet available. Finally, it’s also important to note that tasks within a sync/async block are executed synchronously by default unless you specify it as an async.

Good question Анна, Remember that the semaphore.wait() blocks the thread from executing until the resource is available. If we were to add this line of code to the main thread (outside the queue.async), it'll check if the resource is available. If it is, it will execute normally, otherwise, it'll cause the app to freeze until the resource is available. You can easily simulate this by following these steps: 1. Comment out the semaphore.signal() in the first queue.async block (to make sure the resource is not made available) 2. Move both instances of semaphore.wait() outside their respective queue.async blocks (as mentioned in your question) 3. Change the background color of the view after the second queue.async block (for a visual test) 4. Run the app Notice that the background color was never changed.

@@EmmanuelOkwara Oh, thank you.But I have one more question, if we use enter() on the main thread for dispatch group is it ok?

@@user-mx6hg8vx5o The essence of the enter() is to "indicate" that a block of code has entered into the group, it is safe to put that on the main thread. wait() on the other hand blocks the caller thread so it is usually better to avoid it and maybe go for the notify() instead

Yeah. It’s quite similar.