From 682875cda7cb2f5d20a16dec910e96c674cd9e9b Mon Sep 17 00:00:00 2001
From: Karol Lewandowski <karol.lewandowski@jetbrains.com>
Date: Fri, 21 Feb 2025 12:03:38 +0100
Subject: [PATCH] execution_contexts.topic: Mention in Coroutines Execution
 Context that `blockingContext` is a no-operation function since 2024.2

---
 .../architectural_overview/threading/execution_contexts.topic | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/topics/basics/architectural_overview/threading/execution_contexts.topic b/topics/basics/architectural_overview/threading/execution_contexts.topic
index f5142a0c8..cf5e88fb1 100644
--- a/topics/basics/architectural_overview/threading/execution_contexts.topic
+++ b/topics/basics/architectural_overview/threading/execution_contexts.topic
@@ -53,7 +53,9 @@
                     While code executed in the Coroutine Execution Context should use suspending functions,
                     sometimes it is required to call non-suspending/blocking APIs that use methods such as
                     <code>ProgressManager.checkCanceled()</code> or <code>ModalityState.defaultModalityState()</code>.
-                    Since 2024.2, these methods work as expected without the need to switch to the Blocking Context.
+                    Since 2024.2, these methods work as expected without the need to switch to the Blocking Context
+                    explicitly with <a href="%gh-ic%/platform/core-api/src/com/intellij/openapi/progress/coroutines.kt">
+                        <code>blockingContext()</code></a> (in 2024.2+, it is effectively a no-operation function).
                 </p>
 
                 <tip>