Signals defines a fairly concise interface for interacting with events. You're not "stealing" control from the loop. Rather, think of it more as listening and

Signals defines a fairly concise interface for interacting with events. You're not "stealing" control from the loop. Rather, think of it more as listening and attaching something to an event. For me, it helps to think of signals less as interrupts in a traditional program loop, but as something more akin to events in event-driven environments.