Page MenuHomePhabricator

[avalanche] Use SteadyMilliseconds where possible
ClosedPublic

Authored by Fabien on Sep 28 2023, 12:28.

Details

Reviewers
PiRK
Group Reviewers
Restricted Project
Commits
rABC9e068b92c3af: [avalanche] Use SteadyMilliseconds where possible
Summary

std::chrono::time_point<std::chrono::steady_clock> is a mouthful and doesn't hint about the expected resolution. Use SteadyMilliseconds where due instead as this is already available in our time.h header.
The Now() function is made constexpr to make sure there is no performance cost over using the standard now() function.

There is no change in behavior.

Depends on D14553.

Test Plan
ninja all check-all

Diff Detail

Repository
rABC Bitcoin ABC
Lint
Lint Not Applicable
Unit
Tests Not Applicable