This brings us to the second option. We can write a function, asyncLoadNews(), that will contain the launch() inside it and return the resulting Job. This function can be called without a launch() block regardless of the thread; and by returning the Job, it's possible for the caller to cancel it:
private fun asyncLoadNews() = launch(dispatcher) {
val headlines = fetchRssHeadlines()
val newsCount = findViewById<TextView>(R.id.newsCount)
launch(UI) {
newsCount.text = "Found ${headlines.size} News"
}
}
This function can be called from anywhere in your code without needing to be wrapped, like this:
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_main)
asyncLoadNews()
}
This simplifies the code if the function is called in many places, and it also reduces the flexibility of the function since it will forcefully be executed in a background thread.
It also has the disadvantage that the readability of the code will depend on the correct naming of the function. For example, if you name this implementation loadNews(), the caller of the function may not be aware that this will run asynchronously, and they may not wait for it to complete, which could lead to race conditions or other concurrency issues.