I m implementing a custom `CoroutineDispatcher` that is an i kotlinlang #coroutines

Channels

100daysofkotlin

100daysofkotlin-2021

algolialibraries

android-architecture

android-databinding

androidgithubprojects

androidx-xprocessing

arrow-contributors

beepiz-libraries

cincinnati-user-group

codemash-precompiler

codingconventions

competitive-programming

competitivecoding

compose-android

compose-desktop

compose-ui-showcase

connect-audit-events

cscenter-course-2016

domain-driven-design

effective-kotlin

effectivekotlin

embedded-kotlin

event21-community-content

fb-internal-demo

fluid-libraries

framework-elide

getting-started

github-workflows-kt

graviton-browser

image-processing

intellij-plugins

intellij-tricks

introduce-yourself

java-to-kotlin-refactoring

jhipster-kotlin

jvm-ir-backend-feedback

k2-early-adopters

kotest-contributors

kotlin-by-example

kotlin-data-storage

kotlin-foundation

kotlin-in-action

kotlin-multiplatform-contest

kotlin-pakistan

kotlinforbeginners

kotlingforbeginners

kotlinprogrammers

kotlintest-devs

kotlinultimatechallenge

kotlinx-datetime

lambdaworld_cadiz

language-evolution

language-proposals

leedskotlinusergroup

library-development

machinelearningbawas

myndocs-oauth2-server

navigation-architecture-component

ohio-kotlin-users

pattern-matching

pocketgitclient

practical-functional-programming

prozis-android-backup

python-contributors

realworldkotlin

refactoring-to-kotlin

refreshversions

russian-kotlinasfirst

skia-wasm-interop-temp

sofl-user-group

spring-security

squarelibraries

stayhungrystayfoolish

strife-discord-lib

swagger-gradle-codegen

swiss-user-group

tricity-kotlin-user-group

Title

a

ansman

10/02/2020, 12:13 AM

I'm implementing a custom

CoroutineDispatcher

that is an immediate behavior. I noticed that

dispatchYield

is marked with

@InternalCoroutinesApi

. Can someone confirm that this is there to prevent people from calling the method, not implementing it? Reading the documentation it seems that this is meant for custom dispatchers to implement but that you should avoid calling it manually

e

elizarov

10/02/2020, 7:25 AM

It should be neither used nor implemented. It used to be used in the past internally by

UnconfiedDispatcher

, but it is not used anymore, so it could disappear from API at any time.

Double-checked. It is still used internally to ensure that when you

yield()

inside a

Dispatchers.Default

it is done in a fair way. But not used for "immediate" behavior anymore. For immediate behavior you just return

false

from

isDispatchNeeded

a

ansman

10/02/2020, 4:25 PM

Interesting. That's good to know

This is for AndroidX's PausingDispatcher

Ideally I would like to handle a regular dispatch and a yield dispatch differently

Right now we have a workaround but it's not ideal

7 Views

#coroutines Join Slack