Thank you for this, I was wondering about how a call could get the value (token or error) on the second call while the first one is running, the concept of "cache" was new for me with a little help from Claude to make it more sense (I'm new on this concept) I was able to grasp it better but your Article help me a lot.
Sometimes I find myself saving all this "demo projects" because I'm afraid I wont remember the concepts and I need to come back and remember so also thanks again for the code.
This is probably the best article on modern swift concurrency out there. Thanks for sharing!
Wow, thanks so much for saying!
If you liked this article, you'll love this recent piece on Swift Concurrency I wrote going over the full toolset! https://www.emergetools.com/blog/posts/swift-async-await-the-full-toolkit
Thank you for this, I was wondering about how a call could get the value (token or error) on the second call while the first one is running, the concept of "cache" was new for me with a little help from Claude to make it more sense (I'm new on this concept) I was able to grasp it better but your Article help me a lot.
Sometimes I find myself saving all this "demo projects" because I'm afraid I wont remember the concepts and I need to come back and remember so also thanks again for the code.