-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
harmonize timestamp types #117
Comments
Is there anybody working on this? If not, I can work on it. |
edit: it looks like this is addressed by 9e55a5b actually. @aszepieniec may be waiting on #120 before merging to master. |
Good that a custom |
@aszepieniec With #124 merged, maybe now is a good time to get 9e55a5b into master? I'm guessing there might be some conflicts to resolve. |
Yes it is. No time like the present. |
Various types are used throughout the code base to capture dates (with time). By convention we count the number of milliseconds since the Unix epoch, but even for this number the types
Duration
,u64
, andBFieldElement
are used rather interchangeably. Note thatBFieldElement
is used for consensus-critical data structures such asBlock
andTransaction
.The text was updated successfully, but these errors were encountered: