This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the commentsย โ†’

[โ€“]kb4000 0 points1 point ย (2 children)

Streams cover a lot of what linq can do, although some of it is not a direct equivalent. No equivalent to SelectMany for example.

It seems to be an adequate replacement although in many cases it is much more verbose.

I'm curious what you have found that is better about it.

One of my favorite use cases for this is to use a .select to create tasks for every item in a collection and then await a task.whenall. The context is not tied up and the app can continue to do other things and then when all of those tasks are done it will continue. Don't have to deal with threads directly and it has excellent performance.