Rx: EnumerableEx.For() vs Enumerable.SelectMany()

柔情痞子 提交于 2019-12-03 07:11:51

Good question. They produce the same results but the internal implementations are quite different.

EnumerableEx.For would have been added to System.Interactive to maintain duality between IObservable and IEnumerables. Note that Observable.For and Observable.SelectMany are different:

IObservable<TResult> For<TSource, TResult>(IEnumerable<TSource> source, Func<TSource, IObservable<TResult>> resultSelector)

vs.,

IObservable<TResult> SelectMany<TSource, TResult>(this IObservable<TSource> source, Func<TSource, IObservable<TResult>> selector)

Therefore you'd expect that EnumerableEx.For would have this signature, rather than the one it actually has:

IEnumerable<TResult> For<TSource, TResult>(**IObservable**<TSource> source, Func<TSource, IEnumerable<TResult>> resultSelector)

However, it obviously doesn't take an IObservable source. Perhaps it was meant to. I would ask your question in the Rx forums, to see if the Rx team has an answer.

They look like equivalent functionality to me. SelectMany is an extension method on an IEnumerable and .For is written as a static method on EnumerableEx, so they are called differently.

    foreach(var s in list.SelectMany(Filter))
    {
        // ...
    }

    foreach (var s in EnumerableEx.For(list, Filter))
    {
        // ...
    }

I'm sure there are specific reasons for using each one.

My guess is that SelectMany traverses everything dynamically, whereas Concat (in For) traverses all of its outer IEnumerable elements before starting to register with and iterate over them.

In other words, Concat works with a fixed set of IEnumerable even if it receives them as an IEnumerable. Therefore, in For, the the entire set of IEnumerable is created before even returning the first TResult. In SelectMany, you receive a TResult instantly.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!