From d8888df4b82602f112eaaea6e647cddccf08882b Mon Sep 17 00:00:00 2001
From: Vsevolod Tolstopyatov <qwwdfsad@gmail.com>
Date: Tue, 28 Jun 2022 18:15:47 +0200
Subject: [PATCH] Additional comment in CoroutineScheduler

---
 kotlinx-coroutines-core/jvm/src/scheduling/CoroutineScheduler.kt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kotlinx-coroutines-core/jvm/src/scheduling/CoroutineScheduler.kt b/kotlinx-coroutines-core/jvm/src/scheduling/CoroutineScheduler.kt
index 6b7fecf553..e08d1cef90 100644
--- a/kotlinx-coroutines-core/jvm/src/scheduling/CoroutineScheduler.kt
+++ b/kotlinx-coroutines-core/jvm/src/scheduling/CoroutineScheduler.kt
@@ -683,6 +683,7 @@ internal class CoroutineScheduler(
                  * No tasks were found:
                  * 1) Either at least one of the workers has stealable task in its FIFO-buffer with a stealing deadline.
                  *    Then its deadline is stored in [minDelayUntilStealableTask]
+                 * // '2)' can be found below
                  *
                  * Then just park for that duration (ditto re-scanning).
                  * While it could potentially lead to short (up to WORK_STEALING_TIME_RESOLUTION_NS ns) starvations,