Reuse allocations by reusing state objects. about livesplit-core HOT 1 CLOSED

While Cow kinda seems cool here at first glance, I think it may not be worth it anymore. The problem is that it locks up the timer and potentially, depending on the implementation, the layout too. That's kinda bad, as this means you need to guarantee exclusive access to both the timer and the layout while rendering the layout, which delays the hotkeys even further. I think it makes more sense to invest time in reusable state objects instead. Especially for the formatted times, we can't make use of Cow anyway. However with reusable state objects we could get down to ~0 allocations most of the time, while allowing us to have fully self-contained state objects that don't lock up any of the important objects.

from livesplit-core.