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
It would be nice if try_now would update the internal state of the clock before attempting to return the time. As it currently stands, it is up to the user of the clock to make sure it is updated before they attempt to call try_now. Thoughts?
The text was updated successfully, but these errors were encountered:
seanybaggins
changed the title
Should the Clock trait take a &mut self instead of &self?
Should the try_now method in the Clock trait take a &mut self instead of &self?
Apr 15, 2021
Sorry for the ridiculously long delay in responding. I'm really hoping to get back into a pattern of working on this crate.
In my implementations, I have been reading directly from hardware which doesn't necessitate changing the internal state of the Clock object. Do you have an implementation that would require that?
It would be nice if
try_now
would update the internal state of the clock before attempting to return the time. As it currently stands, it is up to the user of the clock to make sure it is updated before they attempt to calltry_now
. Thoughts?The text was updated successfully, but these errors were encountered: