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.

Sign up for GitHub

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

Jump to bottom

issue-2: adjust "now" to avoid floating point issues; fix a typo #2

Merged
merged 1 commit into from
Apr 11, 2017
Merged

issue-2: adjust "now" to avoid floating point issues; fix a typo #2

merged 1 commit into from
Apr 11, 2017

Conversation

robertmetcalf
Copy link
Contributor

  1. fix a problem where converting the epoch (date/time and microseconds)
    borders on the limits of a 64-bit double-precision floating point number;
    the resulting value is adjusted relative to January 1, 2017.
  2. correct a typo.

@robertmetcalf
issue-1:
4422cb3 
1) fix a problem where converting the epoch (date/time and microseconds)
borders on the limits of a 64-bit double-precision floating point number;
the resulting value is adjusted relative to January 1, 2017.
2) correct a typo.
@robertmetcalf robertmetcalf changed the title issue-1: adjust "now" to avoid floating point issues; fix a typo issue-2: adjust "now" to avoid floating point issues; fix a typo Apr 11, 2017
@rwz rwz merged commit 4d04d10 into rwz:master Apr 11, 2017
@rwz
Copy link
Owner

rwz commented Apr 11, 2017

👍👍👍

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@robertmetcalf @rwz