IRC Logs for #circuits-dev Saturday, 2013-02-02

HI, prologic. Currently, every timer has its own generate_events, so if you have 100 timers (I have a lot in my application) you have 100 handlers for GenerateEvent. The "new" implementation has only a single generate_events in the scheduler, because it maintains a list of timers sorted by expiry time.

We could, but the new implementation is intended as a replacement. Exactly the same API, exactly the same behaviour. Only the implementation differs. So why would we want to keep the old Timer implementation as "SingleTimer"?

Well, you are the native speaker. I thought of a schedule, "a plan" that lists all Timers to be fired (like a flight schedule). It is not a controller that actively schedules something. So from what my dictionary says, I still think that "schedule" describes it better than "scheduler", but English is not my first language.

I re-enabled ci because I saw that timer test failing (in ci only, in my 3.2 environment here it worked). But it really seems to have been a race condition. Now that I set the timer interval from 0.1 to 0.2 in the test there can no longer be any interference with the wait_for checking every 0.1s and it also works in ci. So you can again disable it if you like.