Add argument to sample to sample at the start of a flow instead of the end?
ColtonIdle opened this issue · 5 comments
Use case
I have a stream of items coming in fairly quickly (30 per second) and according to my PMs I only need to grab the first item, every 5 seconds. This is pretty simple with sample(5.seconds), but I always have to wait at least 5 seconds before I get the first element. It'd be awesome in order to control that I want the element from the beginning of the 5 seconds instead of the last element of the 5 seconds.
The Shape of the API
I feel like an argument would suffice, but maybe an enum or something of what type of sampling is being done. Thank you!
Sounds a bit like RxJava's throttleLatest. Does that look like what you're asking for?
That does indeed look like what I'm looking for.
Prior to Compose UI (which arguably has this behavior built-in), this operator was used widely between our data sources and UI. Never loved the name, but was just happy to have it built-in to RxJava after a long time evangelizing it. Conceptually I refer to it as the "at-most-every" operator, since you're basically saying notify me as soon as possible but at most every X seconds.
See #1107 (comment)
@fvasco that looks like a really simple implementation. Much simpler than what sample() is. I'll see if that gets me the behavior I'm looking for. Thanks!