okay, in this case we should just open-code the laziness here; it is only usable within an Actor, so the synchronization barriers for the checks are simply not needed