You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SteadyTime keeps time in nanoseconds, while mio uses delay in ms. If duration between now and timeout time is rounded down when converting to ms, the timer can fire while the precise now is not yet bigger than timeout time. This is not fatal, as the timer will just generate next mio timeout_ms(0), but it's not optimal.
I guess rounding time up when converting to ms is a proper fix.
The text was updated successfully, but these errors were encountered:
dpc
changed the title
It seem Timer can fire prematurely due to resultion differences.
It seem Timer can fire prematurely due to resulution differences.
Aug 27, 2015
dpc
changed the title
It seem Timer can fire prematurely due to resulution differences.
It seem Timer can fire prematurely due to resolution differences.
Aug 27, 2015
dpc
changed the title
It seem Timer can fire prematurely due to resolution differences.
Timer can fire prematurely due to resolution differences.
Aug 31, 2015
SteadyTime keeps time in nanoseconds, while mio uses delay in ms. If duration between now and timeout time is rounded down when converting to ms, the timer can fire while the precise now is not yet bigger than timeout time. This is not fatal, as the timer will just generate next mio
timeout_ms(0)
, but it's not optimal.I guess rounding time up when converting to ms is a proper fix.
The text was updated successfully, but these errors were encountered: