40

Suppose I have the following code:

foreach(string str in someObj.GetMyStrings())
{
    // do some stuff
}

Will someObj.GetMyStrings() be called on every iteration of the loop? Would it be better to do the following instead:

List<string> myStrings = someObj.GetMyStrings();
foreach(string str in myStrings)
{
    // do some stuff
}

?

1
  • 24
    Try it and see - Put a breakpoint in GetMyStrings() and see how many times the debugger stops there!
    – AakashM
    Commented Oct 27, 2009 at 18:38

4 Answers 4

56

The function's only called once, to return an IEnumerator<T>; after that, the MoveNext() method and the Current property are used to iterate through the results:

foreach (Foo f in GetFoos())
{
    // Do stuff
}

is somewhat equivalent to:

using (IEnumerator<Foo> iterator = GetFoos().GetEnumerator())
{
    while (iterator.MoveNext())
    {
        Foo f = iterator.Current;
        // Do stuff
    }
}

Note that the iterator is disposed at the end - this is particularly important for disposing resources from iterator blocks, e.g.:

public IEnumerable<string> GetLines(string file)
{
    using (TextReader reader = File.OpenText(file))
    {
        string line;
        while ((line = reader.ReadLine()) != null)
        {
            yield return line;
        }
    }
}

In the above code, you really want the file to be closed when you finish iterating, and the compiler implements IDisposable cunningly to make that work.

7
  • Correct me if I am wrong, But i think C# compiler does not allow you to edit the IEnumerable while the foreach loop is running. Commented Aug 26, 2016 at 6:37
  • @ShaswatRungta: I don't know what you mean by "edit the IEnumerable" or how this is relevant to the question.
    – Jon Skeet
    Commented Aug 26, 2016 at 6:43
  • If you try to Edit the IEnumerable once the foreach has started executing, the application throws an exception during run time Try to run this code pastebin.com/MztPyiuA . Commented Aug 26, 2016 at 7:22
  • @ShaswatRungta: Compilers can't throw exceptions - they're not involved at execution time. And you still haven't said what you mean by "edit the IEnumerable". I suspect you're getting confused with the safeguards that some collection types (e.g. List<T>) but in place. If you modify a List<T> while you're iterating over it, yes, you'll get an exception. That's a decision made by the List<T> implementation - I don't see how it's relevant to this question.
    – Jon Skeet
    Commented Aug 26, 2016 at 7:23
  • @JonSkeet I thought this was because the List was processed as an IEnumerable for foreach loop and the loop was not allowing it to be edited while iterating over it. [Used the word compiler by mistake. I meant during run time] Commented Aug 26, 2016 at 7:28
19

No.. the function will get called once to get the IEnumerable.. and then there will be repeated call to MoveNext and Current.

4

GetMyStrings() retuns an object of type IEnumerable. The runtime knows how to deal with that. It calls IEnumerable.GetEnumerator() and then on that enumerator object calls MoveNext() and Current.

3

Just to round the question off in case you fall into a "all for's are the same";

for(int x=0;x < ProvideCeiling(); x++)

does call the function each time.

Not the answer you're looking for? Browse other questions tagged or ask your own question.