tree 148eb9d25bb5c8909017301e67cb4bf82b8b3861
parent 1ed19c872e3c283354349ced921d5f039048d4e1
author Vsevolod Tolstopyatov <qwwdfsad@gmail.com> 1677168823 +0300
committer GitHub <noreply@github.com> 1677168823 +0300
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJj95C3CRBK7hj4Ov3rIwAA9S0IAC/pk44nGEEISjy7l+ScU1QZ
 jdno+D9WSJ/QEJMbkiau8fxKf+lo+kRwSDZ9M/WGsZ1u9pQc52D5aCWQW9rjGg8V
 l67WwUdOeiP/qCCneRxsxTwrjwnjk9wjsRX8TpJgIP6mEF/5QPPM5aYzLgqyNCRJ
 gz6e8Xu90nK8rYBu8jvdTNINemhogNPneDMl/CS1CI3mw+Dl1onWZqt3nynFty/Q
 E94tZRGFm6HPIrFAJIH35qO9/wJrbKBw/o8pZQ7Bi2WOhglBQ07thPLsGOzPUMNo
 Y5c5c00cOjerf+Lc7XPmLk/3bhn5wnFtHJVKqFKopKvKe+jCRJkDIdPGm58uyVQ=
 =RFdk
 -----END PGP SIGNATURE-----
 

Change the contract of CoroutineContext.isActive to return 'true' for contexts with no job in it. (#3639)

Otherwise, the API is becoming an error prone for being called from jobless entrypoints (i.e. 'suspend fun main' or Ktor handlers), as 'if (ctx.isActive)' is a well-established pattern for busy-wait or synchronous job.
It is now aligned with CoroutineScope.isActive behaviour.

Fixes #3300