That still doesn't do exactly what a throttle should, but you're reinforcing that the answer is that I need to build it myself.

Coroutines are still young, I agree there's still what to build, but in Rx it's much harder to build... out of curiosity, what's missing from throttle?

it still delays events needlessly

The delay doesn't hold up any threads, so there's no waste

the waste is the time that's delayed when it doesn't need to be

Did you see the 'non-blocking sleep' section in kotlinx.coroutines KEEP document? If you're not holding any threads, I don't see the waste... I think maybe

delay

is maybe a tricky name....

@jw Wouldn't

yield()

do the trick?

That would prevent the event source from doing work. I want to prevent the consumer from doing work.

@jw How does Rx not waste that time, I guess the actual implementation of delay is better, but this is in the KEEP doc:

private val executor = Executors.newSingleThreadScheduledExecutor {
Thread(it, "scheduler").apply { isDaemon = true }
}
suspend fun delay(time: Long, unit: TimeUnit = TimeUnit.MILLISECONDS): Unit = suspendCoroutine { cont ->
executor.schedule({ cont.resume(Unit) }, time, unit)
}

You're probably aware of this, I'm just wondering for myself, I view the code as avoiding the step consumer that Rx would do behind the scenes...

Rx doesn't have this operator

Oh I thought you meant

sample

or similar... if you actually implement something, I'd be very interested in seeing it... thanks @jw!