 loop until a new event arrives,
  presumably via an ISR). Given the relatively few lines of code required to
  implement a custom <code>FifoWorker</code> type and the fact that almost
  all applications will implement at most one such class, it does not seem to
  be worthwhile anyway. Applications requiring a less or more sophisticated
  event processor lifetime management can customize the behavior at a more
  coarse level, by using a custom <code>Scheduler</code> type. This is
  currently also true for a