Captured Closure (Loop Variable) in C# 5.0

by

What is the reasoning behind this?

I’m going to assume you mean “why wasn’t it changed for for loops as well?”

The answer is that for for loops, the existing behaviour makes perfect sense. If you break a for loop into:

  • initializer
  • condition
  • iterator
  • body

… then the loop is roughly:

{
    initializer;
    while (condition)
    {
        body;
        iterator;
    }
}

(Except that the iterator is executed at the end of a continue; statement as well, of course.)

The initialization part logically only happens once, so it’s entirely logical that there’s only one “variable instantiation”. Furthermore, there’s no natural “initial” value of the variable on each iteration of the loop – there’s nothing to say that a for loop has to be of a form declaring a variable in the initializer, testing it in the condition and modifying it in the iterator. What would you expect a loop like this to do:

for (int i = 0, j = 10; i < j; i++)
{
    if (someCondition)
    {
        j++;
    }
    actions.Add(() => Console.WriteLine(i, j));
}

Compare that with a foreach loop which looks like you’re declaring a separate variable for every iteration. Heck, the variable is read-only, making it even more odd to think of it being one variable which changes between iterations. It makes perfect sense to think of a foreach loop as declaring a new read-only variable on each iteration with its value taken from the iterator.

More Related Contents:

  1. Has foreach’s use of variables been changed in C# 5?
  2. Performance difference for control structures ‘for’ and ‘foreach’ in C#
  3. What is the difference between for and foreach?
  4. Closures behaving differently in for and foreach loops
  5. Captured variable in a loop in C#
  6. In .NET, which loop runs faster, ‘for’ or ‘foreach’?
  7. Is a LINQ statement faster than a ‘foreach’ loop?
  8. Update all objects in a collection using LINQ
  9. Using async/await for multiple tasks
  10. Breaking out of a nested loop
  11. What are ‘closures’ in C#? [duplicate]
  12. Using ‘async’ in a console application in C# [duplicate]
  13. Fire-and-forget with async vs “old async delegate”
  14. Using async without await
  15. How does Task become an int?
  16. Foreach loop, determine which is the last iteration of the loop
  17. Best way to convert callback-based async method to awaitable task
  18. Is async/await suitable for methods that are both IO and CPU bound?
  19. Task.Yield – real usages?
  20. Does foreach automatically call Dispose?
  21. foreach with index [duplicate]
  22. Intelligent way of removing items from a List while enumerating in C#
  23. Is the ranged based for loop beneficial to performance?
  24. Why can’t we assign a foreach iteration variable, whereas we can completely modify it with an accessor?
  25. Check for null in foreach loop
  26. Can’t await async extension method
  27. for and while loop in c#
  28. How is foreach implemented in C#? [duplicate]
  29. Why can’t I modify the loop variable in a foreach?
  30. Why can’t I do foreach (var Item in DataTable.Rows)?

Leave a Comment