From b044315b86f4f7d89a51c2cbb5db3a70d49b9e6d Mon Sep 17 00:00:00 2001 From: Karol Lewandowski Date: Tue, 18 Feb 2025 15:03:04 +0100 Subject: [PATCH] coroutine_execution_contexts.md: Add links --- .../coroutines/coroutine_execution_contexts.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/topics/basics/architectural_overview/coroutines/coroutine_execution_contexts.md b/topics/basics/architectural_overview/coroutines/coroutine_execution_contexts.md index 10ed06820..d3e76c27c 100644 --- a/topics/basics/architectural_overview/coroutines/coroutine_execution_contexts.md +++ b/topics/basics/architectural_overview/coroutines/coroutine_execution_contexts.md @@ -170,12 +170,11 @@ The following table presents the possibilities and APIs to use for switching bet - - -

1 blockingContext() enables ProgressManager.checkCanceled(), forwards modality state, etc.

-

2 runBlockingCancellable() has an opposite behavior to blockingContext()

-

3 coroutineToIndicator() is an internal API to aid platform migration

-

4 blockingContextToIndicator() is an internal API to aid platform migration

+ 1 blockingContext() enables ProgressManager.checkCanceled(), forwards modality state, etc. It has an opposite behavior to runBlockingCancellable().
+ 2 runBlockingCancellable() has an opposite behavior to blockingContext()
+ 3 coroutineToIndicator() is an internal API to aid platform migration
+ 4 blockingContextToIndicator() is an internal API to aid platform migration