|
|
|
|
|
by corresation
4484 days ago
|
|
There's no fundamental reason why LINQ to Objects should be any slower than say a foreach over a set. There's no fundamental reason why LINQ to Objects should be any faster than a foreach over a set. Which is precisely the point. LINQ has an amazing way of hiding details in a manner that allows for massively inefficient code to look completely innocuous. For throw-away, one-off "command line utility to convert A to B" type code, it is absolutely golden. For long-term use code that may be called millions of times, it can be disastrous. You have no interest in a reasoned discussion, and your argument style is best described as defensive. That is all. Have a nice day. |
|
I'm out of this thread, it's not adding to the discussion.