Skip to main content
Commonmark migration
Source Link

###Wherein we get a bit too obsessive in making comparisons....

Wherein we get a bit too obsessive in making comparisons....

###Wherein we get a bit too obsessive in making comparisons....

Wherein we get a bit too obsessive in making comparisons....

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

In a comment that was left1, there was a link to an SO question regarding a warning about variable access with foreach and using closureSO question regarding a warning about variable access with foreach and using closure. The part that really caught my eye in that question was that there may have been differences in how the .NET 4.5 compiler worked versus earlier versions of the compiler.

I considered running yet another case that incorporated a closure inside of the foreach loop. But you had asked about the effects of where a primitive type variable was declared, so I figured I was delving too far beyond what you were interested in asking about. The SO question I mentioned earlier has a great answergreat answer that provides a good overview about closure effects on foreach iteration variables.

In a comment that was left1, there was a link to an SO question regarding a warning about variable access with foreach and using closure. The part that really caught my eye in that question was that there may have been differences in how the .NET 4.5 compiler worked versus earlier versions of the compiler.

I considered running yet another case that incorporated a closure inside of the foreach loop. But you had asked about the effects of where a primitive type variable was declared, so I figured I was delving too far beyond what you were interested in asking about. The SO question I mentioned earlier has a great answer that provides a good overview about closure effects on foreach iteration variables.

In a comment that was left1, there was a link to an SO question regarding a warning about variable access with foreach and using closure. The part that really caught my eye in that question was that there may have been differences in how the .NET 4.5 compiler worked versus earlier versions of the compiler.

I considered running yet another case that incorporated a closure inside of the foreach loop. But you had asked about the effects of where a primitive type variable was declared, so I figured I was delving too far beyond what you were interested in asking about. The SO question I mentioned earlier has a great answer that provides a good overview about closure effects on foreach iteration variables.

replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
Source Link

In a comment that was leftIn a comment that was left1, there was a link to an SO question regarding a warning about variable access with foreach and using closure. The part that really caught my eye in that question was that there may have been differences in how the .NET 4.5 compiler worked versus earlier versions of the compiler.

In a comment that was left1, there was a link to an SO question regarding a warning about variable access with foreach and using closure. The part that really caught my eye in that question was that there may have been differences in how the .NET 4.5 compiler worked versus earlier versions of the compiler.

In a comment that was left1, there was a link to an SO question regarding a warning about variable access with foreach and using closure. The part that really caught my eye in that question was that there may have been differences in how the .NET 4.5 compiler worked versus earlier versions of the compiler.

added 120 characters in body
Source Link
user53019
user53019
Loading
added 291 characters in body
Source Link
user53019
user53019
Loading
Wherein we get a bit carried away...
Source Link
user53019
user53019
Loading
added 810 characters in body
Source Link
user53019
user53019
Loading
added 178 characters in body
Source Link
user53019
user53019
Loading
Source Link
user53019
user53019
Loading