public class CoroutineContextKt
| Modifier and Type | Method and Description |
|---|---|
static NonExistentClass |
newCoroutineContext(CoroutineScope $receiver,
NonExistentClass context)
Creates context for the new coroutine. It installs
Dispatchers.getDefault when no other dispatcher nor
ContinuationInterceptor is specified, and adds optional support for debugging facilities (when turned on). |
public static NonExistentClass newCoroutineContext(CoroutineScope $receiver, NonExistentClass context)
Creates context for the new coroutine. It installs Dispatchers.getDefault when no other dispatcher nor
ContinuationInterceptor is specified, and adds optional support for debugging facilities (when turned on).
Debugging facilities: In debug mode every coroutine is assigned a unique consecutive identifier. Every thread that executes a coroutine has its name modified to include the name and identifier of the currently running coroutine. When one coroutine is suspended and resumes another coroutine that is dispatched in the same thread, then the thread name displays the whole stack of coroutine descriptions that are being executed on this thread.
Enable debugging facilities with "kotlinx.coroutines.debug" (DEBUG_PROPERTY_NAME) system property
, use the following values:
"auto" (default mode, DEBUG_PROPERTY_VALUE_AUTO) -- enabled when assertions are enabled with "-ea" JVM option.
"on" (DEBUG_PROPERTY_VALUE_ON) or empty string -- enabled.
"off" (DEBUG_PROPERTY_VALUE_OFF) -- disabled.
Coroutine name can be explicitly assigned using class CoroutineName context element.
The string "coroutine" is used as a default name.
Note: This is an experimental api. Behavior of this function may change in the future with respect to its support for debugging facilities.