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
During the work to expose more free functions on Instant and add mock ability, we created a small rift between Clock and Instant.
Primarily, we have three issues:
Instant::recent will fallback to the global clock, while Clock::recent won't
Instant::recent is an acquire load, while Clock::recent is a relaxed load
quanta::set_recent and Clock::upkeep aren't DRY (small problem, but still)
We should unify these codepaths so that we're limiting the chance for differences in behavior, as well as switching entirely to relaxed loads for "recent" time to ensure maximum performance.
The text was updated successfully, but these errors were encountered:
During the work to expose more free functions on
Instant
and add mock ability, we created a small rift betweenClock
andInstant
.Primarily, we have three issues:
Instant::recent
will fallback to the global clock, whileClock::recent
won'tInstant::recent
is an acquire load, whileClock::recent
is a relaxed loadquanta::set_recent
andClock::upkeep
aren't DRY (small problem, but still)We should unify these codepaths so that we're limiting the chance for differences in behavior, as well as switching entirely to relaxed loads for "recent" time to ensure maximum performance.
The text was updated successfully, but these errors were encountered: