Thread history

Fragment of a discussion from Talk:Wave Surfing/GoTo Surfing
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
No results

My thought are, why take the risk? Making an allocation pool or hoisting the allocation outside of the loop for frequently created/deleted objects is fairly easy. Also less pressure on the GC will make a GC run during your tick less likely, so you are less likely to skip turns. Stack analysis is good, but I'm not sure how it deals with nested objects. I suspect there is still a heap allocation internally, which can be hoisted out of most loops quite easily.

Skilgannon (talk)22:34, 2 September 2017