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
Is there some reason that we have both nix::time::ClockId and nix::sys::timerfd::ClockId? It seems like nix::time::ClockId is more complete - defining more types of clocks for different operating systems. It looks to me like the timerfd implementation could be entirely replaced by the time one.
I would be happy to submit a PR removing nix::sys::timerfd::ClockId (if doing so makes sense). Obviously this would be a breaking change, so it may have to wait.
The text was updated successfully, but these errors were encountered:
It looks like nix::time::ClockId was added fairly recently in #1281. I suggest removing nix::sys::timerfd::ClockId when we're next allowed a breaking change.
Is there some reason that we have both
nix::time::ClockId
andnix::sys::timerfd::ClockId
? It seems likenix::time::ClockId
is more complete - defining more types of clocks for different operating systems. It looks to me like the timerfd implementation could be entirely replaced by the time one.I would be happy to submit a PR removing
nix::sys::timerfd::ClockId
(if doing so makes sense). Obviously this would be a breaking change, so it may have to wait.The text was updated successfully, but these errors were encountered: