The OP wasn't saying, 'this bug isn't a big deal.' He's saying, 'the bug fix shouldn't break existing programs.' Because people, like you, designed around this. Few people, if any, designed their apps to rely on the value in the loop not changing - that's why this 'breaking fix' should break almost no programs.
Re:C# Language Specification 5.0
by seanmcdirmid on Tuesday June 25, 2013 @09:13PM
(#5943505)
Yes, you are right, my reading comprehension of OP's comment sucks.
Same here, it bit me quite a few times and was highly irritating each time. Very annoying to choose between copying the loop variable, or passing it off to some other method to gin up an action/func safely.
It really was a horrible wart that needed to be fixed.
Now if they would only fix the misleading lying dishonest "downcast on type bound" compiler error messages, then C# would lack warts all together.