Skip to content
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

tendermint: remove tai64 crate #603

Merged
merged 1 commit into from
Oct 1, 2020
Merged

tendermint: remove tai64 crate #603

merged 1 commit into from
Oct 1, 2020

Conversation

tony-iqlusion
Copy link
Collaborator

A very long time ago this was used as a (monotonic, leap-second-free) internal representation for the Time type.

It was switched to use chrono::DateTime<Utc> and is now no longer needed.

A very long time ago this was used as a (monotonic, leap-second-free)
internal representation for the `Time` type.

It was switched to use `chrono::DateTime<Utc>` and is now no longer
needed.
@@ -17,26 +16,26 @@ use std::time::{Duration, SystemTime, UNIX_EPOCH};
pub struct Time(DateTime<Utc>);

impl Time {
/// Get a `Timestamp` representing the current wall clock time
/// Get [`Time`] value representing the current wall clock time
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed up some comments here too (the type used to be named [Timestamp] but was renamed to [Time] to better align with the Tendermint spec)

Copy link
Member

@greg-szabo greg-szabo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually did this in my aminoff3 branch too, only I couldn't merge it yet..

@tarcieri tarcieri merged commit 8ec241f into master Oct 1, 2020
@tarcieri tarcieri deleted the remove-tai64 branch October 1, 2020 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants