Why Go for-range behaves differently (A peek into go compiler optimization) | Hacker News Reader