#2 0x0000555555dd216d in std::_replacement_assert(char const*, int, char const*, char const*) In the following example, you can see that the main coroutine is running (we’ve stopped on a breakpoint inside it), and the other four coroutines are suspended: If you started a coroutine with a custom name, you can find it by this name in the Tool Window. The coroutines are grouped by the dispatcher they are running on. In this tab, you can find information about both currently running and suspended coroutines. It is visible by default, and you can switch it on and off: The Debug Tool Window now contains a new Coroutines tab. To address this issue, we’re introducing new functionality in the Kotlin plugin that aims to make debugging coroutines much more convenient. As a result, you have to rely on logging or mental effort to debug the code with coroutines. And in some cases, tracking steps over breakpoints simply doesn’t work. It can be difficult to understand what a specific coroutine is doing or to check its context. When you write code with coroutines, however, trying to debug them can be a real pain. Debugging coroutinesĬoroutines are great for asynchronous programming (but not only for that), and many people already use them or are starting to use them. These changes are already available for you to try in the 1.4.0-RC release! The ability to define deep recursive functions.New functionality to conveniently debug coroutines.In this blogpost, we want to describe a couple of important features related to coroutines: We continue to highlight the upcoming changes in 1.4 release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |