Home/ Questions/Q 7796269
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T23:19:21+00:00

ReSharper refactored a foreach loop I had to something like this. I wanted to

  • 0

ReSharper refactored a foreach loop I had to something like this. I wanted to spawn a bunch of threads via a delegate’s BeginInvoke with different parameters, stored in a list, and store the IAsyncResults in a collection:

var asyncResults = mylist.Select(x => myDelegate.BeginInvoke(x, null, null));

My instinctive reaction is that this is not a good practice. BeginInvoke is causing a side effect of a new thread being spawned, and functions passed to Select should not cause side effects.

Or maybe it’s ok, because I’m not altering anything in the calling thread?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think it’s hard to tell whether this is a good practice or not, it depends on how are you using it.

    But the important thing to remember when using LINQ like this is that Select() (and many other LINQ methods) doesn’t actually iterate over the collection and execute your code. That happens only when you iterate over the resulting collection, usually using foreach or ToArray().

    • 0