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
The jb::microbenchmark class needs a steady clock to perform relative measurements. The class uses std::steady_clock because it is always guaranteed to have this property. However, we could determine at compile-time if std::high_resolution_clock is also steady (using the is_steady static member variable). If it is steady then it is a "better" choice (or at least no worse choice).
In most implementations this will have no effect, but this issue documents the choices we have made for future reference.
The text was updated successfully, but these errors were encountered:
The jb::microbenchmark class needs a steady clock to perform relative measurements. The class uses std::steady_clock because it is always guaranteed to have this property. However, we could determine at compile-time if std::high_resolution_clock is also steady (using the is_steady static member variable). If it is steady then it is a "better" choice (or at least no worse choice).
In most implementations this will have no effect, but this issue documents the choices we have made for future reference.
The text was updated successfully, but these errors were encountered: