I get that I should not hardcode dispatchers in my repos, viewmodels, etc. But what if I want to switch Dispatcher in an extension function of some data class?

suspend fun List<TaskStatistic>.getCurrentCompletedStreak(): Int =
    withContext(Dispatchers.Default) {
        var currentStreak = 0
        for (statistic in this@getCurrentCompletedStreak.reversed()) {
            if (!statistic.taskCompleted) break
            currentStreak++
        }
        currentStreak
    }

Two thoughts: 1. You could use

coroutineScope { }

to inherit the calling scope/context 2. This is something that multiple receivers will alleviate

i feel like my design must be wrong because I don't like either of those options

Does that need to be a suspend function? Let the caller decide I think.

ok makes sense

To replace the for loop.

ok, thank you

You can also pass a Dispatcher to the function, which is mostly the same as letting the caller decide, but it allows you to be more targeted about what goes on that dispatcher (e.g. if you only want a specific section of the function to go there)

yea it just feels weird to declare dispatcher arguments for these functions