Hacker News Reader

C# had the exact same pitfall and it was recognised years ago. It's unfortunate that it made it in to Go.

Did they introduce a language solution for it in C#?

C# 5.0 is changing the behavior of the loop variable to be logically inside the loop [0].