Even more so, if you’re calling a function that creates a different thread to run in, you can’t return a value to the outer function. One of the biggest problems in computing is being able to return values from asynchronous functions. Sounds too good to be true? Well you’ll see how all of this functionality is actually an old concept, so let’s get going! The async/await pattern They can also return values, as if you’re calling a standard function. In this chapter, you’ll see how you can build similar mechanisms which aren’t blocking and can work asynchronously and in parallel. These functions were actually blocking but could have been asynchronous. You also saw how you can migrate from callback-based APIs to ones that are coroutine-based, which has the signature of a regular function returning the value you need when called. So far you’ve seen how coroutines and suspendable functions can be used to bridge threads and execute asynchronous work that doesn’t add much overhead to your program. 12.1 Getting started with broadcast channels.10.5 Yield and YieldAll at your service.Building Sequences & Iterators with Yield Section II: Channels & Flows Section 2: 6 chapters Show chapters Hide chapters 1.9 Explaining coroutines: The inner works.1.7 Diving deeper into the complexity of Rx.1.6 Using reactive extensions for background work.
1.4 Handling work completion using callbacks.1.3 Interacting with the UI thread from the background.Section I: Introduction to Coroutines Section 1: 9 chapters Show chapters Hide chapters
0 kommentar(er)
