Kirill Rakhman

This could be made easier if we extended the `IPointEmitter` interface, but this would be a breaking change if I'm not mistaken.

@MarcinMoskala it's just to differentiate. I use `apply` when I need to the receiver as the return value, otherwise I don't use it.

I think you're missing the `inline` modifier.

To me, the name of the issue is not very clear. Which statements exactly are meant? I think loops deserve a separate issue where the pros and cons as well...

You can use the other `when` syntax: ``` kotlin val scope = when { includeNonProjectItems -> GlobalSearchScope.allScope(project) else -> GlobalSearchScope.projectScope(project) } ```

@nblumhardt I will rework the PR. I'll implement a similar mechanism to the current batching approach where data will be periodically aggregated and then flushed down the pipeline.

@nblumhardt I've finished the rework. I've reimplemented the aggregation to run periodically, just like the batching. They also both derrive from the same base class now. Because the aggregation now...

@nblumhardt I think I've found a solution for the problem described above. Points within the timer interval, i.e. inside `[now - interval, now]` now always land inside the same bucket....

@nblumhardt did you have time to look at the PR?

@nblumhardt Thanks for the reply. I misunderstood your last comment but I think I get your point now. For sums, the bucket approach seems ideal. Other kinds of aggregations can...