Add metered

[vpavkin]

No description provided.

[pchlupacek]

Not sure about the name here. I think this is related to scheduling and perhaps we have somehow express this. Something like iterateAtRate or similar.

[vpavkin]

@pchlupacek I named it consistently with awake family (awakeEvery). But iterateAtRate also fits.
I'm fine with both.

Actually, pronouncing iterateAtRate feels a bit awkward :)

[pchlupacek]

I am not expert on the naming these mouthful operators. Lets see what @SystemFw @mpilquist thinks about this.

[pchlupacek]

My whole idea is that awake sort of implies the scheduling, where iterate does not plus, we already use iterate for bunch of scheduling unrelated methods.

[SystemFw]

iterateEvery is fine as a name, it's consistent with awakeEvery. I'm slightly more doubtful that this op warrants inclusion (you can add an *Every to every op in the lib), but not really opposed to it either, whatever you guys prefer

[vpavkin]

Also, as side note we could make perhpas metered to be more effective than zipping, by just inserting it at every value emitted.... like this.evalMap { a => Timer.sleep(d) as a }

Doesn't this change the semantics from fixedRate to fixedDelay?

[SystemFw]

this sense smthing like atMaxRateOf could be more precise

That's not the case, if the other stream is slower it will be slower.

ike this.evalMap { a => Timer.sleep(d) as a }

These semantics are different, that's fixedDelay, not fixedRate

[pchlupacek]

yeah it does. :-)

[vpavkin]

@SystemFw

if the other stream is slower it will be slower.

I might be wrong, but I think that's what maxRate implies - if this is too fast, the rate is limited, but if it's slow, the rate is slow as well.

metered is more concise though, I'll go with it.

[SystemFw]

I might be wrong, but I think that's what maxRate implies

nah, you're right, the ratio there got me :P

[vpavkin]

I've spent like 15 min on the scala doc, but still feel it can be worded better :)