3 ms·

Good nitpicking. But as you indicated, the change of behaviour should only affect people with a very dubious/interesting approach.

• seanmcdirmid 13y ago
  No, this bug was encountered often by myself and many of my colleagues. Because I was so familiar with the problem, I could guess that this was a problem in their code after looking at it for a few seconds. 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.
  • sk5t 13y ago
    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.
  • pixie_ 13y ago
    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.
    • seanmcdirmid 13y ago
      Yes, you are right, my reading comprehension of OP's comment sucks.