Yes, because if the loop is not always-executing, it may be cheaper to not initi... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		DannyBee on Oct 22, 2017 \| parent \| context \| favorite \| on: Debunking the Java Performance Myth Yes, because if the loop is not always-executing, it may be cheaper to not initialize the complex object, even if it is safe to so.

yoklov on Oct 24, 2017 [–]

I've also (recently) had poor performance on MSVC when "outside the loop" meant "a function argument", for a type that was essentially a struct wrapping a single primitive. It ended up being ABI weirdness that was confusing MSVC (and forceinline ended up fixing it).

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact