You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They are defined in terms of concatMap, however we can define them in terms of ++, the strict implementation (not the one with the by-name param, after #643 happens).
So the challenge, should you choose to accept it:
provide an implementation based on ConcatObservable instead of fromIterable and concatMap
prove that it is better by a benchmark, you can dump a quick benchmark in the benchmarks sub-project ... but don't commit it in the PR
The text was updated successfully, but these errors were encountered:
I've tried to provide some implementation by stacking sources into ConcatObservable. It ended up with sth like that:
def concat[A](sources: Observable[A]*): Observable[A] =
sources.toList.foldLeft(Observable.empty[A])((acc, a) => new ConcatObservable[A](acc, a))
In benchmark I've generated 3k Observable containing pure Int and then applied my implementation of concat to them. But the performance was terrible.
Current implementation is:
Currently we've got these functions on the companion object:
They are defined in terms of
concatMap
, however we can define them in terms of++
, the strict implementation (not the one with the by-name param, after #643 happens).So the challenge, should you choose to accept it:
ConcatObservable
instead offromIterable
andconcatMap
benchmarks
sub-project ... but don't commit it in the PRThe text was updated successfully, but these errors were encountered: