why .net c# lack of "EACH"

Question

Possible Duplicate:
is there a .Each() (or .ForEach() ) iterator in the .Net standard library?

Maybe I am wrong, but I don't see the "EACH" function in .net (3.0)?

We can

IEnumerable<T>.Select().Where().First().Any()

Why don't we have

IEnumberable<T>.Each(Action<T> action)?

So instead of 2 lines: Foreach(T t in list) action(t);

we can just call list.Each((t)=>{blah;blah;})?

Is there a concern for performance?

See [this question](http://stackoverflow.com/questions/2230538/foreach-in-or-foreach-that-is-the-question) and it's answers. — Hans Keﬆing, Feb 28 '11 at 12:08
This one has an answer too: http://stackoverflow.com/questions/858978/lambda-expression-using-foreach-clause/859068#859068 — Daniel A. White, Feb 28 '11 at 12:09

score 2 · Answer 1 · answered Feb 28 '11 at 12:07

2

Frequently asked, definitively answered:

http://blogs.msdn.com/b/ericlippert/archive/2009/05/18/foreach-vs-foreach.aspx

answered Feb 28 '11 at 12:07

Daniel Earwicker

114,894
38
205
284

+1 I always wondered about that myself... thanks for the interesting link! – Mark Carpenter Feb 28 '11 at 12:13

score 1 · Answer 2 · answered Feb 28 '11 at 12:08

1

List.ForEach

answered Feb 28 '11 at 12:08

Flagbug

2,093
3
24
47

score 0 · Answer 3 · answered Feb 28 '11 at 12:08

0

It was made this way, since none of the extention methods on IEnumerable was supposed to have any side effects, and a ForEach would have side effects as it's primary objective.

It was deemed that a foreach loop is not much more verbose to write out.

answered Feb 28 '11 at 12:08

Øyvind Bråthen

59,338
27
124
151

why .net c# lack of "EACH"

3 Answers3